-
|
Hi, I have developed a simple Direct Forwarding solution, using the basic example. endpoints.Map("/{**catch-all}", async httpContext =>
{
var error = await forwarder.SendAsync(httpContext, "https://example.com", httpClient, requestOptions, transformer);
if (error != ForwarderError.None)
{
var errorFeature = httpContext.Features.Get<IForwarderErrorFeature>();
var exception = errorFeature.Exception;
}
});I am using this to forward the requests to different destinations, depend on some conditions. For most sites it works great, but for one I get the following exception. It would be great if anyone has any suggestions on how to resolve this. {"Received chunk header length could not be parsed: '3C-21-44-4F-43-54-59-50-45-20-48-54-4D-4C-20-50-55-42-4C-49-43-20-22-2D-2F-2F-57-33-43-2F-2F-44-54-44-20-48-54-4D-4C-20-34-2E-30-31-20-54-72-61-6E-73-69-74-69-6F-6E-61-6C-2F-2F-45-4E-22-3E'."} Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Can you capture a wireshark trace? We'd need to see what headers accompany that response. That error implies that there was a |
Beta Was this translation helpful? Give feedback.
-
|
The server is replying with invalid HTTP. It is specifying There is no way to control this internal behavior of Do you have the option to change/fix the server behavior here (either add proper chunk framing, or avoid adding the header)? |
Beta Was this translation helpful? Give feedback.
-
|
@lahiru119 do you know what is the server "Rapid Logic/1.1". Per @MihaZupan's internet search it may be some kind of embedded device. There may be similar problem with it from 2006 reported on curl: https://curl.se/mail/lib-2006-04/0046.html |
Beta Was this translation helpful? Give feedback.
-
|
Hi All, Thanks for your replies. @MihaZupan we are unable change/fix the server side of things. @karelz Yes, the server is on an embedded device. And we can successfully load the web page if we access directly via any web browser. I will look into your suggestions. Thanks again. Really appreciate your help. |
Beta Was this translation helpful? Give feedback.
-
|
Given that this is server problem and it is violating RFC, we do not plan to address it in HttpClient. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @karelz , I managed to get it working by following the link you provided (https://curl.se/mail/lib-2006-04/0046.html). Thanks a lot for that. And thanks to everyone too. |
Beta Was this translation helpful? Give feedback.
Can you capture a wireshark trace? We'd need to see what headers accompany that response. That error implies that there was a
Transfer-Encoding: chunkedheader, but that the body wasn't formatted correctly. Those bytes decode as follows, which is not using the chunking format.<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">