add response-outparam.send-informational
#139
Merged
Conversation
This file contains 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 believe the CI failure is due to a bug in how |
|
The CI failure should be addressed by bytecodealliance/wasm-tools#1958 once that fix makes its way to a |
lukewagner
approved these changes
Dec 18, 2024
This allows a server to send zero or more HTTP 1xx responses prior to sending the final response using `response-outparam.set`. Note that this does not include support for consuming informational responses for outbound requests (which would be required to losslessly proxy such requests). Signed-off-by: Joel Dice <[email protected]>
Signed-off-by: Joel Dice <[email protected]>
dicej
force-pushed
the
send-informational
branch
from
7687721 to
a377bea
Compare
Signed-off-by: Joel Dice <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows a server to send zero or more HTTP 1xx responses prior to sending the final response using
response-outparam.set.Note that this does not include support for consuming informational responses for outbound requests (which would be required to losslessly proxy such requests).