fix: generalize the http status code returned to nginx when required#86
Open
asteed wants to merge 2 commits intoadobe-apiplatform:masterfrom
Open
fix: generalize the http status code returned to nginx when required#86asteed wants to merge 2 commits intoadobe-apiplatform:masterfrom
asteed wants to merge 2 commits intoadobe-apiplatform:masterfrom
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
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.
In older OpenResty versions, NGINX was more lenient with invalid status codes.
In NGINX 1.27.1, it strictly validates that HTTP status codes must be between
100-599, so codes emitted by the gateway (ie:401013) can cause unexpected failuresThis fix is to replace a detailed status with it's generalization. For example:
401013becomes401