On Tuesday 31 May 2011 17:24:55 Brian E. Lozier wrote:
This is helpful, thank you. If the logic for having plack/psgi apps behind a proxy is already handled in Plack::Middleware::ReverseProxy, why is this happening again in Dancer? Is there an intention for Dancer app developers to use Plack::Middleware modules or have all the "important" ones recreated inside Dancer? Is there an advantage to using behind_proxy => 1 vs. using Plack::Middleware::ReverseProxy directly? It looks like all the middleware does is reset some environment variables so the Dancer app will think it's being run directly.
It's a pretty important feature which is going to be required by some people, and some people could object to installing additional modules to make it work. Feel free to use Plack::Middleware::ReverseProxy instead though if you're happy to install it :) Cheers Dave P -- David Precious ("bigpresh") http://www.preshweb.co.uk/ "Programming is like sex. One mistake and you have to support it for the rest of your life". (Michael Sinz)