On Tue, Apr 16, 2013 at 02:06:30AM +0400, Maxim Dounin wrote:
> On Mon, Apr 15, 2013 at 10:42:30PM +0100, Francis Daly wrote:
> > On Mon, Apr 15, 2013 at 05:35:27PM -0400, jaychris wrote:
Hi there,
> > > client sent invalid header line: "X_FORWARDED_PROTO: http" while reading
> > > client request
Hello!
On Mon, Apr 15, 2013 at 10:42:30PM +0100, Francis Daly wrote:
> On Mon, Apr 15, 2013 at 05:35:27PM -0400, jaychris wrote:
>
> Hi there,
>
> > I was using the X_FORWARDED_PROTO header to make some decisions on the
> > backend when I was using Apache, but it doesn't look like Nginx is han
Thanks! Setting "underscores_in_headers on;" fixed the issue and
X_FORWARDED_PROTO is being carried forward now.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238384,238387#msg-238387
___
nginx mailing list
nginx@nginx.org
http://mailman.ng
On Mon, Apr 15, 2013 at 05:35:27PM -0400, jaychris wrote:
Hi there,
> I was using the X_FORWARDED_PROTO header to make some decisions on the
> backend when I was using Apache, but it doesn't look like Nginx is handling
> the header currently:
>
> client sent invalid header line: "X_FORWARDED_PR
Running Nginx 1.2.7 behind HAproxy, with SSL being terminated on on HAproxy.
I was using the X_FORWARDED_PROTO header to make some decisions on the
backend when I was using Apache, but it doesn't look like Nginx is handling
the header currently:
client sent invalid header line: "X_FORWARDED_PROTO