404 responses when dispatcher calls publisher on secure port | Community
Skip to main content
W
webbCBS
Level 2
August 30, 2017
Solved

404 responses when dispatcher calls publisher on secure port

  • August 30, 2017
  • 3 replies
  • 1528 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by webbCBS

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

3 replies

W
webbCBSAuthor
Level 2
August 31, 2017

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.

W
webbCBSAuthorAccepted solution
Level 2
September 27, 2017

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

Terms & ConditionsAccessibility statement

Loading footer...