The proxy path in AEM has no bearing on publish.  Proxy path is purely for author.  AEM author ships with an internal proxy (via code) that is not available on the publisher.  What you need to ensure is that your dispatcher proxy is set up and pointing to Adobe I/O, and that should be that.  Can you...

So you get a 503 error when going through the dispatcher, but a 200 when you go directly to Adobe I/O?  I think I'll need a little more info to help.  My use-case from this original post was using a third-party commerce system through Adobe I/O as well, so I know it's possible.  In that case, I reme...

You should be able to proxy your local Magento installation the same way you would proxy to the cloud instance.  The Adobe CIF GraphQL Proxy Configuration doesn't exist in publish which is exactly why you need to use your dispatcher as the proxy instead of relying on the proxy that ships with AEM Au...

@icegoffy it looks like you're deploying wknd code.  Is there a reason you're needing to update indexes on the wknd project?  Normally you would start building project code from a fresh codebase generated from the latest archetype?  It's possible there's something in the wknd codebase that is causin...

No you need to add a proxy in your dispatcher that does this.  Look at the code he posted above, that is included in the CIF: # CQ-4287185: Allow access to magento reverse-proxy endpoint<IfDefine COMMERCE>    SSLProxyEngine on    <LocationMatch "/api/graphql">        ProxyPass        ${COMMERCE_ENDP...

This is the right way to do it, I forgot the CIF team had added this into the codebase now.  I haven't been working on the CIF for a minute, but now I remember that they added this code in.  I should probably upgrade ours to use the CIF version of the reverse proxy rather than our custom one It work...

I updated my local dispatcher tools to have an ENVIRONMENT_LOCAL option, and then use that in conjunction with an addition I made to our vhost file like this:<IfDefine ENVIRONMENT_LOCAL> ProxyErrorOverride off ProxyPass /api/graphql http://host.docker.internal:3001 ProxyPassReverse ...

For 500 errors, you need to set up the error page to 301 redirect to another page.  This will interrupt the redirect chain that Adobe has in place to send you to their error page.  So basically set up your error page to point to/my-custom-error-pageand then in your rewrite rules, set up a 301 redire...

That's awesome, I'm glad it worked!  This was driving me nuts, and I happened upon the Jackrabbit Jira ticket where this was discussed and resolved, so I was bent on making it work as soon as I saw that the validator was fixed!

Hi everyone! I was struggling a bit with this topic, so figured I'd post a discussion to help any others who are having issues.  The setup to load new or updated oak indexes into the cloud is fairly simple, and there's already documentation on how to do this...however, with the latest version of the...