AEM Cloud - Set-cookie Missing From ProxyPassReverse Request

[edufc]

Hi,

I'm in the process of migrating to AEM Cloud Service and I needed to enable the dispatcher's ProxyPassReverse to make an api call. However, upon receiving the response, all the headers of the api response are present. Except SET-COOKIE. I looked in the dispatcher files and they don't have anything blocking this specific header.

In the current project with the Managed Service, I had the same problem only on CloudFront. There I had to change a cookie setting, so that it would allow the SET-COOKIE to be sent to the browser along with the other headers.

Has anyone had this problem or know how to help?

[SantoshSai]

Hi @edufc ,

The dispatcher allows you to filter headers, which are then forwarded to the AEM instance (or blocked). 

Make sure that these headers are provided there, as they are not included by default.

See the documentation here:  https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c...

Hope that helps!

Regards,

Santosh

[edufc]

Hi @SantoshSai , thanks for reply.

I already tried to add in all the configurations that involve the dispatcher header, including /clientheaders and none works.

As I configured a reverse proxy like the example below, the dispatcher does not send the request to the AEM instance, it makes the request to the configured endpoint itself.

<IfModule mod_proxy.c>
	SSLProxyEngine on   		

	ProxyPass /home https://domain/home/
	ProxyPassReverse /home https://domain/home/	
</IfModule>

When I do this same test with the local dispatcher, I have no problem, all response headers are returned. Only in the Adobe Cloud that the SET-COOKIE header is removed and all other custom headers, which are not even configured in the dispatcher files, are sent to the browser.

[edufc · Accepted solution]

Just an update. This problem is internal to Adobe's infrastructure, it was necessary to open a ticket and they are still analyzing it.

No deadline for resolution.