404 responses when dispatcher calls publisher on secure port

[webbCBS]

I appreciate that this question may be somewhat abstract, however I hope maybe someone has seen something similar and can offer a resolution?

My infrastructure is set up as follows:

F5 load balancer  forwards requests to  Apache version 2.4.6 configured with dispatcher version 4-4.1.12

Dispatcher connects to AEM  6.1 SP2-CFP4 publish instance.  Unsecured port 4503, SSL port 5434

When the dispatcher.any file is configured to point to the unsecured 4503 port on the publish server, all valid requests, sent initially to the F5 are served up as expected.

However, when the dispatcher is reconfigured to point to the secure port on the publish server, the same requests via the F5, which previously succeeded, now return a 404 error.

To make it more interesting, if the same request is initiated directly via the dispatcher server, whilst sill configured to point to the publishers secure port, then the request again succeeds.

All pages are requested with a ? appended to avoid dispatcher caching them, and all https responses have been observed in the publishers access.log.

Hopefully I have explained myself clearly.  I would appreciate any assistance that could be offered.

Many thanks.

[smacdonald2008]

After checking with internal experts - they stated:

"

My best guess is that they don’t use Apache with SSL i.e.

Instead of https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher/_jcr_content/top/... they use

https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher/_jcr_content/top/...

"

[webbCBS]

Hi.

Thank you for your quick response.  I am still confused however, as to how this will help.

My confusion stems from the fact, that if you make the request from a browser
https://<dispatcher_server>/content/mypage.html?   Then the request succeeds.

But the same request to https://<loadbalancer>/content/mypage.html results in the 404 error.

When the request is made via the load balancer, you can see in the dispatcher servers access logs, the same  GET request received, which previously succeeded.

Thanks in advance for any help.

[webbCBS · Accepted solution]

Issue turned out to be incorrect application configuration in /etc/map/https. redirecting requests to the wrong location.