<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello<br>
<br>
see my rewrite log<br>
<br>
init rewrite engine with requested uri /website/about<br>
applying pattern '^/website/(.*)' to uri '/website/about'<br>
rewrite '/website/about' -> '/'<br>
applying pattern '^/(.*)' to uri '/'<br>
rewrite '/about' -> '<a class="moz-txt-link-freetext" href="http://localhost:5002/about">http://localhost:5002/about</a>'<br>
forcing proxy-throughput with <a class="moz-txt-link-freetext" href="http://localhost:5002/about">http://localhost:5002/about</a><br>
go-ahead with proxy request proxy:<a class="moz-txt-link-freetext" href="http://localhost:5002/about">http://localhost:5002/about</a> [OK]<br>
<br>
but /about route do not existe, this is /website/about and I've got
a 404...<br>
<br>
It seems like Rewrite Rules is not a possible ( or if I create fake
routes /about....)<br>
<br>
<br>
<div class="moz-cite-prefix">Le 22/10/2015 18:02, John J. McDermott,
CPLP a écrit :<br>
</div>
<blockquote cite="mid:562908AF.6010201@jkintl.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I think I have this right. The doc says
<blockquote>The RewriteRule directive is the real rewriting
workhorse. The directive can occur more than once, with each
instance defining a single rewrite rule. The order in which
these rules are defined is important - this is the order in
which they will be applied at run-time.<br>
</blockquote>
<br>
Your <font face="Courier New, Courier, monospace">RewriteRule
^/website/(.*) /</font> rule appears to get rid of everything
after the first "/" in the case of /website. The second rule has
nothing to operate on for /website. So<br>
whate.ver/website/contact becomes<br>
whate.ver/<br>
<br>
Also note that context is important. Again from the doc<a
moz-do-not-send="true" id="what_is_matched"
name="what_is_matched">What is matched?</a>
<div class="note">
<blockquote>
<p>In <code class="directive"><a moz-do-not-send="true"
href="http://httpd.apache.org/docs/current/mod/core.html#virtualhost">VirtualHost</a></code>
context, The <em>Pattern</em> will initially be matched
against the part of the URL after the hostname and port, and
before the query string (e.g. "/app1/index.html").</p>
<p>In <code class="directive"><a moz-do-not-send="true"
href="http://httpd.apache.org/docs/current/mod/core.html#directory">Directory</a></code>
and htaccess context, the <em>Pattern</em> will initially
be matched against the <em>filesystem</em> path, after
removing the prefix that led the server to the current <code
class="directive">RewriteRule</code> (e.g.
"app1/index.html" or "index.html" depending on where the
directives are defined).</p>
<p>If you wish to match against the hostname, port, or query
string, use a <code class="directive"><a
moz-do-not-send="true"
href="http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewritecond">RewriteCond</a></code>
with the <code>%{HTTP_HOST}</code>, <code>%{SERVER_PORT}</code>,
or <code>%{QUERY_STRING}</code> variables respectively.</p>
</blockquote>
</div>
<br>
<br>
--john<br>
<br>
<div class="moz-cite-prefix">On 10/22/2015 9:49 AM, Hugues wrote:<br>
</div>
<blockquote cite="mid:5629057D.4050608@max4mail.com" type="cite">Hello
<br>
I use perl dancer with Apache in mod_proxy + starman.pl <br>
<br>
<br>
ProxyPass / <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://localhost:5002/">http://localhost:5002/</a>
retry=0 Keepalive=on <br>
ProxyPassReverse / <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://localhost:5002/">http://localhost:5002/</a>
<br>
<br>
I've got path like <br>
/website/about <br>
/website/contact <br>
etc..; <br>
<br>
for <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="http://www.mydomain.com">www.mydomain.com</a> <br>
I would like to rewrite url <br>
<br>
/about <br>
/contat <br>
etc.. <br>
<br>
I try with <br>
<br>
RewriteRule ^/website/(.*) / <br>
RewriteRule ^/(.*) <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://localhost:5002/$1">http://localhost:5002/$1</a>
[P] <br>
<br>
<br>
but result is no good, I go to /.... <br>
<br>
if someone has a idea ? <br>
Thanks <br>
<br>
Hugues. <br>
_______________________________________________ <br>
dancer-users mailing list <br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:dancer-users@dancer.pm">dancer-users@dancer.pm</a>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://lists.preshweb.co.uk/mailman/listinfo/dancer-users">http://lists.preshweb.co.uk/mailman/listinfo/dancer-users</a>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
John J. McDermott, CPLP<br>
Learning and Performance Consultant<br>
jjm at jkintl.com 575/737-8556<br>
Check out my <a moz-do-not-send="true"
href="http://cybersecurity.learningtree.com"> security blog
posts</a><br>
Add an A for the Arts To STEM and get STEAM and a strong engine
to move forward. </div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dancer-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dancer-users@dancer.pm">dancer-users@dancer.pm</a>
<a class="moz-txt-link-freetext" href="http://lists.preshweb.co.uk/mailman/listinfo/dancer-users">http://lists.preshweb.co.uk/mailman/listinfo/dancer-users</a>
</pre>
</blockquote>
<br>
</body>
</html>