Re: X-Forwarded-Proto / X_FORWARDED_PROTO

2010-01-09 Thread skaar
The Rack (and CGI) specs require that '-' be replaced with '_' for HTTP header names, so Unicorn is doing the correct thing and treating it as the same header. but should it aggregate the values? Even though '_' appears to be allowed in header names by rfc 2616, it's use is questionable

Re: X-Forwarded-Proto / X_FORWARDED_PROTO

2010-01-09 Thread Iñaki Baz Castillo
El Domingo, 10 de Enero de 2010, skaar escribió: The Rack (and CGI) specs require that '-' be replaced with '_' for HTTP header names, so Unicorn is doing the correct thing and treating it as the same header. but should it aggregate the values? Hi, review my other response in this

Re: X-Forwarded-Proto / X_FORWARDED_PROTO

2010-01-09 Thread Eric Wong
Iñaki Baz Castillo i...@aliax.net wrote: El Domingo, 10 de Enero de 2010, skaar escribió: The Rack (and CGI) specs require that '-' be replaced with '_' for HTTP header names, so Unicorn is doing the correct thing and treating it as the same header. but should it aggregate the

Re: X-Forwarded-Proto / X_FORWARDED_PROTO

2010-01-09 Thread Eric Wong
Eric Wong normalper...@yhbt.net wrote: Iñaki Baz Castillo i...@aliax.net wrote: In your case it seems valid for me (just an opinnion) as HTTP_X_FORWARDED_PROTO: http,https could mean that the request has been sent using HTTPS and an intermediary proxy has forwarded it using HTTP. Of