-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A sample nginx configuration #6
Comments
I don't want to include a full proxy profile because different users have different needs, but i think your point about including some notes about X-Forwarded-Proto is a good one, i can add that to the readme |
Thanks, this helped me out a tonne :-) |
I know this is not a real issue but it might be good to include the necessary configurations to setup a reverse proxy. The following code snippet can be great help to others since the application requires some headers to be set and most browsers give mixed content error if the headers are not in place.
Shortly, at least the following headers should be set:
The other's are not required to make CSS and JS files load correctly, however can be useful for other purposes.
One possible solution to remove the protocol dependency is to call the styles and scripts by omitting the protocol and letting the browser handling it: //domain.com/stlye.css
I tried to find where this is being set but couldn't navigate myself safely in Haskell code.
The text was updated successfully, but these errors were encountered: