Use SoapServer headers #16859
Merged
Use SoapServer headers #16859
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
Superkooka
approved these changes
Oct 27, 2022
While debugging the istio error `Error dispatching received data: http/1.1 protocol error: HPE_UNEXPECTED_CONTENT_LENGTH` we noticed that the error was [triggered](https://github.com/nodejs/http-parser/blob/e13b274/http_parser.c#L1442) because of a duplicated Content-Length headers being send by the PHP application. After review we noticed that the header was send by both the SoapServer and the Symfony Response for this reason I decided to open this PR.
javiereguiluz
force-pushed
the
patch-1
branch
from
d7b0de5 to
4717f04
Compare
|
Thank you @boekkooi. |
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.
While debugging the istio error
Error dispatching received data: http/1.1 protocol error: HPE_UNEXPECTED_CONTENT_LENGTHwe noticed that the error was triggered because of a duplicated Content-Length headers being send by the PHP application.After review we noticed that the header was send by both the SoapServer and the Symfony Response for this reason I decided to open this PR.