Hi sebastian,<div><br></div><div>   good to know that the fault was on my side of the question, there&#39;s always space for learning something :-)</div><div><br></div><div>Unfortunately I don&#39;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.</div>

<div><br></div><div>I addressed the problem and solved it with a new uri_for function, I&#39;m curious whether others had the same problem or know more &quot;streamline&quot; solutions.</div><div><br></div><div>Cheers,</div>

<div><br></div><div>   Flavio.</div><div><br></div><div><br><div class="gmail_quote">On Fri, Dec 17, 2010 at 12:12 PM, sebastian de castelberg <span dir="ltr">&lt;<a href="mailto:sebu@kpricorn.org">sebu@kpricorn.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">hi,<br>
<div class="im"><br>
&gt; Wow! Maybe I was a bit too verbose, I&#39;ll try to condense in two simple<br>
&gt; questions:<br>
</div>much better...;)<br>
<div class="im"><br>
&gt; 1. is it possible to set up uri_for to play well in a reverse-proxy<br>
&gt; environment?<br>
</div>in case your app runs with plack, you may have a look at<br>
<a href="http://search.cpan.org/~danjou/Plack-Middleware-ReverseProxy-0.06/" target="_blank">http://search.cpan.org/~danjou/Plack-Middleware-ReverseProxy-0.06/</a>.<br>
if I recall correctly, a redirect issue we had could be fixed with<br>
this plugin. it could work for uri_for too.<br>
<div class="im"><br>
&gt; 2. what is the best approach to handle static content in a reverse-proxy<br>
&gt; environment, i.e. having the reverse-proxy handle it directly?<br>
</div>In our low-traffic setup Dancer delivers static content (deployment<br>
was much easier).<br>
<br>
cheers<br>
</blockquote></div><br></div>