Hi,

On Sat, Sep 22, 2012 at 4:23 PM, Filipe Silva <fs20063@outlook.com> wrote:

> Hi,
>

[...]

I'm taking a look at apache default configuration to check if there is
> something that is making nginx behave differently. Below are the
> response headers from each case:
>
> Response headers from reverse proxy nginx 80
>
> HTTP/1.1 200 OK
> Server: nginx/1.3.5
> Date: Sat, 22 Sep 2012 08:13:08 GMT
> Content-Type: text/html
> Content-Length: 163
> Connection: keep-alive
> Last-Modified: Thu, 06 Sep 2012 13:39:44 GMT
> Etag: "81333-b1-4c9089fc7c802"
> Vary: Accept-Encoding
> Content-Encoding: gzip
>
> Response headers from web server apache 8080
>
> HTTP/1.1 200 OK
> Date: Sat, 22 Sep 2012 08:13:13 GMT
> Server: Apache/2.2.16 (Ubuntu)
> Last-Modified: Thu, 06 Sep 2012 13:39:44 GMT
> Etag: "81333-b1-4c9089fc7c802"
> Accept-Ranges: bytes
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Content-Length: 146
> Keep-Alive: timeout=15, max=100
> Connection: Keep-Alive
> Content-Type: text/html
>
> On the meanwhile if you have a clue what is happening I'll be thankful.
>

Please turn off gzip on Apache side then try again :)

Regards,

--
Joshua Zhu
Senior Software Engineer
Server Platforms Team at Taobao
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel