We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Setting up a project I came across an issue where pages where returning 502 status codes. After debugging the issue I found this to be the solution to the problem: https://ma.ttias.be/nginx-proxy-upstream-sent-big-header-reading-response-header-upstream/
This needs to be added to the nginx configuration files.
The text was updated successfully, but these errors were encountered:
@dcabrejas does this still need adding? if so can you PR it so I don't get it wrong.
BTW, if you want to test nginx changes on a real project, just edit the nginx file in place and then run
wf2 dc exec nginx nginx -s reload
Sorry, something went wrong.
I am not sure, I think it still needs adding althought I haven't had this problem for a long time.
Thanks for the tip 😃
dcabrejas
No branches or pull requests
Setting up a project I came across an issue where pages where returning 502 status codes.
After debugging the issue I found this to be the solution to the problem:
https://ma.ttias.be/nginx-proxy-upstream-sent-big-header-reading-response-header-upstream/
This needs to be added to the nginx configuration files.
The text was updated successfully, but these errors were encountered: