Reread the documentation and what the flag is actually about. You are disabling (off) a feature which IGNORES invalid header names. If you rely on invalid header names, you need to enable this feature, not disable it.

And btw, the feature is already on by default, so why don't you just remove it from the configuration?


That being said, you should absolutely not rely on invalid headers, since that may break in certain browsers.
Are you perhaps confusing CUSTOM (X-blabla: asdasd) with INVALID header names (broken-§$%&\/()-header-name: asdasd)?






----------------------------------------
> To: nginx@nginx.org
> Subject: Re: RE: About ignore_invalid_headers directive in SSL
> From: nginx-forum@nginx.us
> Date: Wed, 23 Jan 2013 06:29:18 -0500
>
> Hi!
>
> Sorry...
>
> When i say "not working" meant that not working ignore_invalid_headers off
> directive.. not propage my customs headers.
>
> My example:
>
> server {
> listen 443;
> ssl on;
> ssl_certificate my_public.crt;
> ssl_certificate_key my_server.key;
> server_name myservername;
> ignore_invalid_headers off;
> location / {
> proxy_pass_header Server;
> proxy_set_header Host $http_host;
> proxy_redirect off;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Scheme $scheme;
> proxy_pass http://192.168.1.82;
> }
> }
>
>
> Thanks!
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,235422,235452#msg-235452
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx