Forum: NGINX About ignore_invalid_headers directive in SSL

Posted by sdeancos (Guest)
on 2013-01-22 17:55
(Received via mailing list)
Hi!

I have a problem.

I have try ignore invalid headers with directive ignore_invalid_headers 
off
in my configuration with SSL and dont get it working, however without 
SSL
perfect work.

What could be the problem?

Thanks!

Posted at Nginx Forum: 
http://forum.nginx.org/read.php?2,235422,235422#msg-235422
Posted by Lukas Tribus (Guest)
on 2013-01-22 18:26
(Received via mailing list)
Please be more specific about SSL "not working".
What does actually happen?
Do you see errors in the Browser?
Do you see errors in access or error logs?
Would you post your relevant configuration please?

Also, sinceignore_invalid_headers has nothing to do with SSL
at all [2], why do you think are trying to fix a SSL related
problem with it? What do you expect from that command?



[2]http://nginx.org/en/docs/http/ngx_http_core_module...


----------------------------------------
Posted by sdeancos (Guest)
on 2013-01-23 12:29
(Received via mailing list)
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
Posted by Lukas Tribus (Guest)
on 2013-01-23 15:29
(Received via mailing list)
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?


Thatbeingsaid, 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)?






----------------------------------------
Posted by Valentin V. Bartenev (Guest)
on 2013-01-23 15:36
(Received via mailing list)
On Wednesday 23 January 2013 15:29:18 sdeancos wrote:
>   listen 443;
>             proxy_set_header X-Scheme $scheme;
>             proxy_pass http://192.168.1.82;
>         }
>     }
>
>
> Thanks!
>

Is this the default server? Do you have other server blocks that listen 
on 443?

Please note from the documentation:

  "A directive can be specified on the server level in a default server. 
In this
   case, its value will cover all virtual servers listening on the same 
address
   and port." @ http://nginx.org/r/ignore_invalid_headers

  wbr, Valentin V. Bartenev

--
http://nginx.com/support.html
http://nginx.org/en/donation.html
Posted by sdeancos (Guest)
on 2013-01-23 16:13
(Received via mailing list)
Thanks very much for all!

Effectively, it was because I had another virtualhost and was not 
putting
the flag. Now it working!

Thanks!!

Posted at Nginx Forum: 
http://forum.nginx.org/read.php?2,235422,235474#msg-235474
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.