search for: http_x_forwarded_proto

...I came across an issue with the parser in unicorn, with a request (due to 2 layers of nginx proxying) coming across with both a X_FORWARDED_PROTO and a X-Forwarded-Proto header. From the socket (in HttpRequest) - we get: X_FORWARDED_PROTO: http X-Forwarded-Proto: https which is parsed to HTTP_X_FORWARDED_PROTO"=>"http,https There was a passenger ticket that describes that from nginx''s point of view - X-Forwarded-Proto is the "correct" form. -- /skaar skaar at waste.org where in the W.A.S.T.E is the wisdom s_u_b_s_t_r_u_c_t_i_o_n

I am trying to move a Rails application, that uses SSL, from an Apache/FastCGI stack, that works fine, to Apache22 and mongrel working with a single mongrel instance (i.e., not mongrel cluster, yet.) I have a single mongrel instance demonized and working fine on http, on port 3000. Apache/OpenSSL/certs working fine. Here is my test http.conf (deliberately kept as simple as possible):

...?ad=5&cid=7 * HTTP_USER_AGENT : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 * HTTP_VERSION : HTTP/1.0 * HTTP_X_BROWSER_TIMESTAMP: 386789 * HTTP_X_FORWARDED_FOR : xx.xxx.xxx.xxx * HTTP_X_FORWARDED_HOST : foo.com * HTTP_X_FORWARDED_PROTO : https * HTTP_X_FORWARDED_SERVER : foo.com * HTTP_X_NAVID : f5c-50cfb * PATH_INFO : /ad_keywords/new * QUERY_STRING : cid=7&ad=5&ct= * RAW_POST_DATA : Connection: Keep-Alive ad_keyword%5Bsmart_keywords%5D=Non+Emergency+Transport+%0...

...p;cid=7 * HTTP_USER_AGENT : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 * HTTP_VERSION : HTTP/1.0 * HTTP_X_BROWSER_TIMESTAMP: 386789 * HTTP_X_FORWARDED_FOR : xx.xxx.xxx.xxx * HTTP_X_FORWARDED_HOST : foo.com * HTTP_X_FORWARDED_PROTO : https * HTTP_X_FORWARDED_SERVER : foo.com * HTTP_X_NAVID : f5c-50cfb * PATH_INFO : /ad_keywords/new * QUERY_STRING : cid=7&ad=5&ct= * RAW_POST_DATA : Connection: Keep-Alive ad_keyword%5Bsmart_keywords%5D=Non+Emergency+Transp...

On my server, stunnel is running to accept HTTPS (port 443) connection from clients and redirect them to localhost:80. And on port 80 of my server, WEBrick is running to accept HTTP connection. In such situation, WEBrick generates URLs beginning with ''http://'', not with ''https://''. So one can access to ''https://myserver/'', but when he click on

Hi all, I''m currently trying to get Mongrel running my app whilst fronted by apache 2.2 in a sub-directory via https. A bit convoluted I''ll grant you but necessitated by existing systems. The pertinent parts of my httpd.conf: <VirtualHost 123.123.123.123:12345> #historic choice of random port number DocumentRoot /var/www/admin ServerName admin.example.com:12345

Hi, I''ve recently been trying to setup Mongrel behind Pound so that I can do mutual SSL authentication. I''ve had a few problems with Pound (documented at [1]), but now have it working correctly. However, I think there is a problem with Mongrel and how it deals with the headers Pound adds to the HTTP header block. One of the extra headers Pound adds is