Secure URL on a Dispatcher instance trying to get contents from publisher | Community
Skip to main content
Level 2
October 16, 2015
Solved

Secure URL on a Dispatcher instance trying to get contents from publisher

  • October 16, 2015
  • 1 reply
  • 560 views

We have a Secure URL on a Dispatcher instance. When we access it with an empty cache, instead of looking to the render and generating folders/files, it registers a "file not found" error for the first directory and gives up/returning a 404 for all the css, js, images etc.

When the URL is hit on the non-secure port, render is accessed, the files and folders are created and there is no error.

Hitting the URL on the Secure port again after that causes no errors as well, because the files and folders now exist from the non-secure Port access.

Can someone please comment how an HTTPS dispatcher URL get the contents from the publish renderer which is HTTP?

Thank you.

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 vsharm3

It has been resolved. We found that apache web server was using the HTTP dispatcher url for pass through for HTTPS URL and that is why it was always using the HTTP virtual host entry at the dispatcher.

1 reply

vsharm3AuthorAccepted solution
Level 2
October 16, 2015

It has been resolved. We found that apache web server was using the HTTP dispatcher url for pass through for HTTPS URL and that is why it was always using the HTTP virtual host entry at the dispatcher.