Welcome! Log In Create A New Profile

Advanced

Re: Backend responding with 100 Continue results in the actual response being lost

July 23, 2013 07:53AM
Hello Maxim,

Thanks for your recommendations. I realise that what this server is doing is a bit unusual, however:

> That is, it's 100 Continue isn't expected to be returned to nginx
> from a complaint HTTP/1.1 server even if a request is via
> HTTP/1.1.

I just wanted to clarify that the server *is* conditionally compliant with HTTP/1.1, since this is a "SHOULD" requirement. Would be nice if this were supported, since otherwise you get timeouts that are very hard to explain and debug (but are easily attributable to nginx's proxying).

In any case. I'm glad I got to the bottom of this very puzzling issue, and that future googlers will finally find something when googling for "nginx 100 continue timeout".
SubjectAuthorPosted

Backend responding with 100 Continue results in the actual response being lost

rstarkovJuly 22, 2013 08:20PM

Re: Backend responding with 100 Continue results in the actual response being lost

Maxim DouninJuly 23, 2013 07:22AM

Re: Backend responding with 100 Continue results in the actual response being lost

rstarkovJuly 23, 2013 07:53AM

Re: Backend responding with 100 Continue results in the actual response being lost

Piotr SikoraJuly 23, 2013 09:48PM

Re: Backend responding with 100 Continue results in the actual response being lost

Maxim DouninJuly 24, 2013 03:34AM

Re: Backend responding with 100 Continue results in the actual response being lost

Piotr SikoraJuly 24, 2013 03:46AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 61
Record Number of Users: 5 on November 05, 2014
Record Number of Guests: 210 on November 05, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready