[Dancer-users] Config Setting "behind_proxy: true" gives incorrect proxied protocol

[Gurunandan Bhat]

Thanks Brian.

I am currently attempting to see if setting one of the environment
variables *__FORWARDED_PROTOCOL_* to "https" and see if it solves the
problem. If it does not I will try your suggestion

Thank you once again



On Wed, Apr 4, 2012 at 9:47 PM, Brian E. Lozier <brian at massassi.com> wrote:

> On Wed, Apr 4, 2012 at 5:56 PM, Gurunandan Bhat <gbhat at pobox.com> wrote:
> > Hi,
> >
> > I am hosting a Dancer Web Application behind an Apache proxy using the
> > recommended (in Dance::Deployment) configuration.
> >
> > The application can be accessed via a secure URL:
> https://some.domain.com
> > and I have set 'behind_proxy: "true"' in my config.yml. However when I
> use
> > [% request.uri_base %], I get http://some.domain.com and not
> > https://some.domain.com which is what I am expecting.
> >
> > Is there a way to have request.uri_base return the correct proxied
> protocol
> > (in this case https) rather than 'http'?
>
> I believe I may have had the same problem (been a while, sorry), and
> ended up using Plack::Middleware::ReverseProxy instead.  My config.yml
> has this:
>
> plack_middlewares:
>  -
>    - Plack::Middleware::ReverseProxy
>
> > Thank you
> > - Gurunandan
> >
> > _______________________________________________
> > Dancer-users mailing list
> > Dancer-users at perldancer.org
> > http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20120405/871d2bdd/attachment.htm>