-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
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
Fix HttpRequest Body Being Consumed and Sending an Empty Request Body #14915
Fix HttpRequest Body Being Consumed and Sending an Empty Request Body #14915
Conversation
/azp run java - appconfiguration - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
…ix version checks
/azp run java - appconfiguration - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - formrecognizer - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - textanalytics - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
/check-enforcer override |
Overriding check-enforcer as Azure Pipelines cancelled a couple pipelines which caused it to never report passing. |
This PR resolves a bug where pipeline operations, such as authorization handling, would consume the
HttpRequest
ByteBuffer
body leading to an empty request body being sent. To resolve the issue theByteBuffer
creation is deferred and made replayable so that any side-affect operation won't leave the body empty when the request is finally sent.#14917 acts as a follow-up to validate locations where
HttpRequest
bodies are consumed to ensure this issue doesn't happen again.#14918 acts as another follow-up to add a
From Source
test run to the daily live tests.