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:Alan Williamson (alan@public.gmane.org)
Date:Aug 29, 2008 4:46:52 am
List:ru.sysoev.nginx

By default all headers goes to backend as is. There are two exceptions:

1) Host: nginx sets it to $proxy_host value, 2) Connection: nginx sets it "close"

okay thats that bit cleared up. thank you.

As I have said before nginx does not remove "Accept-Enconding" by default.

okay, i think the clue may lie in the fact nginx proxies in only "HTTP/1.0". So i would have to override the backend to break the protocol slightly here, and if receive a request in HTTP/1.0 *but* still can accept GZIP then give it.

Why only 1.0 incidentally?

As I understand EC2 cloud are Amazon servers. Are your backends EC2 servers ?

yes, but i suspect you don't have much experence in this world. Amazon has nothing to do with it, they are merely a cloud provider. The instances are running OUR software, on OUR Linux setup. I shouldn't have brought it up, as it appears to be 'clouding' the issue! :)

-- Alan Williamson Registrationless email/sms reminders: http://yourli.st/ blog: http://alan.blog-city.com/