4 messages in ru.sysoev.nginxRe: Reverse Proxy Load Balancing - pr...
FromSent OnAttachments
Dustin KanskeMar 9, 2007 3:13 pm 
Igor SysoevMar 9, 2007 10:42 pm 
Dustin KanskeMar 16, 2007 5:42 pm 
Igor SysoevMar 31, 2007 1:42 pm 
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: Reverse Proxy Load Balancing - proxy_set_headerActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Mar 9, 2007 10:42:10 pm
List:ru.sysoev.nginx

On Fri, Mar 09, 2007 at 01:13:42PM -1000, Dustin Kanske wrote:

In my nginx config I am attempting to set the values of two request headers using the following configuration:

location / { proxy_set_header X_FORWARDED_PROTO http; proxy_set_header X_SSL_VERIFIED false; }

The goal is to ignore whatever the client sets for these headers, and to pass our defined values on to the upstream cluster.

It appears that these values only get set if the client leaves them out of the request. If the client sets X_SSL_VERIFIED to true, the backend application sees 'true'.

I wanted to clarify that this is the expected behavior and that proxy_set_header cannot be used to override the request header values that a client sets. If this is the case, is there any way to accomplish this?

No, proxy_set_header always resets any client header. Are you shure that you do not mix X_SSL_VERIFIED and X-SSL-VERIFIED ?