On 1 Jul 2014 07:58, Lucas Rolff lu...@slcoding.com wrote:
Hi guys,
I'm currently running nginx version 1.6.0 (after upgrading from 1.4.4).
Sadly I've found out, after upgrading proxy_pass_header seems to stop
working, meaning no headers is passed from the upstream at all
You need to read
Well, it used to work before 1.6.0..
For me
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_header
shows that I should do:
proxy_pass_header Cache-Control;
So that should be correct
Best regards,
Lucas Rolff
Jonathan Matthews wrote:
On 1 Jul 2014 07:58, Lucas Rolff
On 1 Jul 2014 10:20, Lucas Rolff lu...@slcoding.com wrote:
Well, it used to work before 1.6.0..
For me
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_header
shows that I should do:
proxy_pass_header Cache-Control;
So that should be correct
No. You have misread the
On 1 Jul 2014 10:34, Lucas Rolff lu...@slcoding.com wrote:
Do you have a link to a documentation that has info about this then?
Because in the below link, and in
http://wiki.nginx.org/HttpProxyModule#proxy_pass_header theres nothing
about what it accepts.
How about the doc you already found,
So.. Where is the thing that states I can't use proxy_pass_header
cache-control, or expires? :)))
Maybe I'm just stupid
Best regards,
Lucas Rolff
Jonathan Matthews wrote:
On 1 Jul 2014 10:34, Lucas Rolff lu...@slcoding.com
mailto:lu...@slcoding.com wrote:
Do you have a link to a
On 1 Jul 2014 11:01, Lucas Rolff lu...@slcoding.com wrote:
So.. Where is the thing that states I can't use proxy_pass_header
cache-control, or expires? :)))
The proxy_hide_header and proxy_pass_header reference docs.
___
nginx mailing list
I've verified that 1.4.4 works as it should, I receive the cache-control
and expires headers sent from upstream (Apache 2.4 in this case),
upgrading to nginx 1.6.0 breaks this, no config changes, nothing.
But thanks for the explanation Robert!
I'll try investigate it further to see if I can
I've been investigating, and seems like it's related to 1.6 or so -
because 1.4.2 and 1.4.4 works perfectly with the config in the first email.
Any that can possibly reproduce this as well?
Best regards,
Lucas R
Robert Paprocki wrote:
Can we move past passive aggressive posting to a public
On Tuesday 01 July 2014 10:30:47 Lucas Rolff wrote:
I've verified that 1.4.4 works as it should, I receive the cache-control
and expires headers sent from upstream (Apache 2.4 in this case),
upgrading to nginx 1.6.0 breaks this, no config changes, nothing.
But thanks for the explanation
nginx:
curl -I http://domain.com/wp-content/uploads/2012/05/forside.png
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 01 Jul 2014 10:42:06 GMT
Content-Type: image/png
Content-Length: 87032
Last-Modified: Fri, 08 Mar 2013 08:02:48 GMT
Connection: keep-alive
Vary: Accept-Encoding
ETag: 51399b28-153f8
You need to examine traffic over the wire between the proxy and the
origin as you send a request from an outside client to the proxy. This
will allow you to see if the origin is even returning the expected
headers to the proxy, or if the proxy is seeing a different response
than a direct client
Hello!
On Tue, Jul 01, 2014 at 01:00:05PM +0200, Lucas Rolff wrote:
nginx:
curl -I http://domain.com/wp-content/uploads/2012/05/forside.png
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 01 Jul 2014 10:42:06 GMT
Content-Type: image/png
Content-Length: 87032
Last-Modified: Fri, 08 Mar 2013
But if files was served from backend I would assume to see the
$upstream_response_time variable in nginx would return other stuff than
a dash in 1.4.4
Like this, using logformat:
$request$status$body_bytes_sent$http_referer$http_user_agent$request_time$upstream_response_time';
GET
Hello!
On Tue, Jul 01, 2014 at 02:33:54PM +0200, Lucas Rolff wrote:
Hmm, okay..
Then I'll go back to an old buggy version of nginx which gives me the
possibility to use the headers from Backend!
You don't need to go back (and I doubt it will help) - if you
don't want nginx to serve files
14 matches
Mail list logo
