fix(nginx): Handle large header responses for root #13803
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will add the sign-off later today. If you auto-block PRs based on linting errors, it would be great to get notified by a comment. I only noticed the failing check because I still had the PR open in a browser tab from yesterday. Also, a PR template pointing with a short checklist of what you expect would be useful. |
See https://help.nextcloud.com/t/resolved-502-on-nextcloud-root-after-update/233954/11. Signed-off-by: Marcel Schilling <[email protected]>
mschilli87
force-pushed
the
fix-nginx-502-root-url-large-response-header
branch
from
e3d04cc to
568c29c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
🖼️ Screenshots
I do not know how to locally build and render the documentation but I only added a few lines to the sample
nginxconfig files that fix an issue I faced after upgrading to NC32.