-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Batch operation results in 'Error parsing HTTP message header byte 101 of message System.Byte[].' #19
Comments
@troygNZ Thankyou for your bug report. |
Thanks @iwate Response example Content-Type: application/json
Content-Length: 118
location:
dataserviceversion: 2.0
{"error":{"code":"","message":{"lang":"en","value":"E-mail address blah;;blah.coom isn't valid. Please check."}}}
Request example, with some sensitive data etc removed or adjusted
|
@troygNZ thanks! I check it out. |
memo: |
ParseState.Invalid from InternetMessageFormatHeaderParser. |
@troygNZ Could you check line break code of the response? It need to be CRLF(0x0d0x0a) |
Thanks @iwate - I'll check this in the morning. The payload and response I obtained for you was from the OData monitoring tool within SAP C4C, so may not preserve it within the browser monitoring tool. I'll debug and reproduce in the IDE to ensure no tampering of response. |
When calling an endpoint that contains a non 200 response for one of the calls, I get back
Error parsing HTTP message header byte 101 of message System.Byte[].
Note, not for all calls.
at System.Net.Http.HttpContentMessageExtensions.<ReadAsHttpResponseMessageAsyncCore>d__19.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at ODataHttpClient.ODataClient.<ParseMultiAsync>d__18.MoveNext()
Quite possibly similar to the problem seen here
https://forums.asp.net/t/2037342.aspx?Max+header+size+when+serializing+HttpMessageContent
Note, this is for an OData 2.0 endpoint.
The text was updated successfully, but these errors were encountered: