[Dancer-users] Reverse-proxy deployments

[Flavio Poletti]

Hi sebastian,

   good to know that the fault was on my side of the question, there's
always space for learning something :-)

Unfortunately I don't think that the Plack solution is going to work,
according to the documentation it should mangle HTTP Headers but uri_for is
geared to the generation of the Body.

I addressed the problem and solved it with a new uri_for function, I'm
curious whether others had the same problem or know more "streamline"
solutions.

Cheers,

   Flavio.


On Fri, Dec 17, 2010 at 12:12 PM, sebastian de castelberg <sebu at kpricorn.org
> wrote:

> hi,
>
> > Wow! Maybe I was a bit too verbose, I'll try to condense in two simple
> > questions:
> much better...;)
>
> > 1. is it possible to set up uri_for to play well in a reverse-proxy
> > environment?
> in case your app runs with plack, you may have a look at
> http://search.cpan.org/~danjou/Plack-Middleware-ReverseProxy-0.06/.
> if I recall correctly, a redirect issue we had could be fixed with
> this plugin. it could work for uri_for too.
>
> > 2. what is the best approach to handle static content in a reverse-proxy
> > environment, i.e. having the reverse-proxy handle it directly?
> In our low-traffic setup Dancer delivers static content (deployment
> was much easier).
>
> cheers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20101217/633974a3/attachment.htm>