-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12-06-18 05:10 AM, Loic d'Anterroches wrote: > Hello, > > short question. What is preventing a 1.8 release of Mongrel2? Do you > think we can set a date to do a release this summer? > > This way we can start to work on the many things people need which could > affect the backward compatibility like HTTPS header or > TRUSTED_HEADER_FOO etc. > > loïc
I haven't had the time to submit a patch, but my recommendation would be to ship 1.8 with the remote IP on both x-forwarded-for and REMOTE_IP, so people can start using REMOTE_IP before x-forwarded-for gets restored to the original header received. That is is we agree to go this route. I personally think as far as handlers are concerned there should be a clear distinction between the headers received and the server variables. OTOH for proxied requests Mongrel2 should append to the XFF header. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/ftdoACgkQ6dZ+Kt5BchYq9QCfb91YUKfO7bUs38yjxTTR6ZLB ABwAnAmriIZTY0GNKe2f9RNDl99EsLYu =ir5q -----END PGP SIGNATURE-----
