Welcome! Log In Create A New Profile


Having dot in the header name

Vinay Y S
January 22, 2010 01:42PM
I see that nginx as proxy rejects headers with name like "auth.client" or
"auth.token" (with dot in their name) and stops parsing further headers.
Thus the request to the upstream server doesn't contain these headers. From
the logs, it says "client sent invalid header line".

Why is having a dot in the header name considered invalid? I searched the
relevant RFCs (2616 and 822) and they don't seem to exclude dot. May I know
the reason for nginx to reject headers with dot while other servers like
Apache httpd parse headers with dot just fine.

Also, in the nginx source I noticed a undocumented directive
"ignore_invalid_headers" which is on by default. It when set to off, makes
nginx passes such headers to the upstream server properly.

Is it safe to use this directive? Are there any side-effects, performance
issues related to using it?

nginx mailing list
Subject Author Posted

Having dot in the header name

Vinay Y S January 22, 2010 01:42PM

Re: Having dot in the header name

Maxim Dounin January 22, 2010 02:30PM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 55
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready