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"
Accept-Ranges: bytes

Backend:

curl -I http://domain.com:8081/wp-content/uploads/2012/05/forside.png
HTTP/1.1 200 OK
Date: Tue, 01 Jul 2014 10:42:30 GMT
Server: Apache
Last-Modified: Fri, 08 Mar 2013 08:02:48 GMT
Accept-Ranges: bytes
Content-Length: 87032
Cache-Control: max-age=2592000
Expires: Thu, 31 Jul 2014 10:42:30 GMT
Content-Type: image/png

So backend returns the headers just fine.

Best regards,
Lucas Rolff


Valentin V. Bartenev wrote:
> 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 Robert!
>> I'll try investigate it further to see if I can find the root cause,
>> since for me this is very odd that it's suddenly not sent to the client
>> anymore.
>>
> [..]
>
> They can be not sent because your backend stopped returning them for some
> reason. Try to investigate what happens on the wire between your backend
> and nginx.
>
> wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx