11 messages in ru.sysoev.nginxRe: GZIP problem with backend hosts
FromSent OnAttachments
Alan WilliamsonAug 28, 2008 4:36 am 
ngin...@public.gmane.orgAug 28, 2008 9:22 am 
Alan WilliamsonAug 29, 2008 1:41 am 
Igor SysoevAug 29, 2008 1:54 am 
Alan WilliamsonAug 29, 2008 3:04 am 
Igor SysoevAug 29, 2008 3:15 am 
Alan WilliamsonAug 29, 2008 4:07 am 
Igor SysoevAug 29, 2008 4:26 am 
Olivier BonvaletAug 29, 2008 4:32 am 
Alan WilliamsonAug 29, 2008 4:46 am 
Igor SysoevAug 29, 2008 4:58 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: GZIP problem with backend hostsActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Aug 29, 2008 1:54:55 am
List:ru.sysoev.nginx

On Fri, Aug 29, 2008 at 09:41:42AM +0100, Alan Williamson wrote:

no one got anything input here?

seems to be a fairly big failing in NGINX here. Why would it spend extra time and resources decompressing outgoing content

nginx can not decompress proxied response. In your case probably backend sends uncompressed response.

Alan Williamson wrote:

Afternoon all.

I first of all thought I had a problem with our backend hosts not sending GZIP content, but it appears NGINX is at fault.

We use nginx infront of a lot of Amazon instances. The backend instances, prepare the content in GZIP'd form.

However nginx, is taking this content, and then decompressing it, and giving out the decompressed version back to the originating client!!

I do not want nginx to do the compressing; the load can be better handled with the backend instances. I just want nginx to proxy what its given and not do too much to the stream coming back.

Advice please?

-- Igor Sysoev http://sysoev.ru/en/