fix(ext-plugin): avoid using 0 as the default http status code #4734
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
spacewander
reviewed
Aug 2, 2021
spacewander
reviewed
Aug 2, 2021
t/plugin/ext-plugin/http-req-call.t
Outdated
| ext.go({stop = true, stop_no_code = true}) | ||
| } | ||
| } | ||
| --- error_code: 200 |
Member
There was a problem hiding this comment.
We already check if error_code == 200 by default
spacewander
reviewed
Aug 2, 2021
spacewander
approved these changes
Aug 3, 2021
tokers
approved these changes
Aug 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does / why we need it:
If the plugin-runner sends a stop request but does not set an Http Status Code, APISIX will use 0 as the default status code, causing the current request to run later phases.
see: apache/apisix-java-plugin-runner#55
Pre-submission checklist: