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 3:37:09 am
List:ru.sysoev.nginx

On Wed, Aug 24, 2011 at 08:53:45AM +0100, James Fidell wrote:

On 24/08/11 07:14, Maxim Dounin wrote:

I suspect that you aren't using the config you provided above, but instead additionally have something like ssi enabled, i.e. something like

ssi on; ssi_types application/x-javascript;

also present in your config.

Unfortunately not :(

It isn't the config that I'll be using in production, but with the exception of a couple of lines I'm hoping are not relevant to the problem, it is the config that I'm using to try to track down what's going wrong. For completeness though, here's what I have:

# cat nginx.conf worker_processes 1;

events { worker_connections 1024; }

http { upstream app { server localhost:8080; }

server { listen 80;

location / { proxy_pass http://app; # proxy_pass_header Content-Length; } } }

nginx running with that configuration produced exactly the output from wget that I showed in my original email.

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

-- Igor Sysoev

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