atom feed9 messages in ru.sysoev.nginxRe: Content-Length header missing aft...
FromSent OnAttachments
James FidellAug 23, 2011 11:43 am 
Geoge.QAug 23, 2011 10:26 pm 
Maxim DouninAug 23, 2011 11:13 pm 
James FidellAug 24, 2011 12:45 am 
James FidellAug 24, 2011 12:52 am 
Igor SysoevAug 24, 2011 3:37 am 
James FidellAug 24, 2011 4:19 am 
Igor SysoevAug 24, 2011 5:20 am 
Matthias R. W.Sep 6, 2011 7:03 am 
Subject:Re: Content-Length header missing after proxying
From:Igor Sysoev (ig@sysoev.ru)
Date:Aug 24, 2011 5:20:50 am
List:ru.sysoev.nginx

On Wed, Aug 24, 2011 at 12:20:49PM +0100, James Fidell wrote:

On 24/08/11 11:37, Igor Sysoev wrote:

Then only debug log may help: http://nginx.org/en/docs/debugging_log.html

And it did. Thank you.

When I connect to the application with wget it uses HTTP/1.1, which gets a content-length header in the response. nginx is connecting using HTTP/1.0, which doesn't.

I'm guessing there's not a whole lot I can do about that?

It's strange that the application sends Content-Length for HTTP/1.1. It's valid header in HTTP/1.0. HTTP/1.1 allows to send chunked response without length.

-- Igor Sysoev

_______________________________________________ nginx mailing list ngi@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx