Joshua Slive wrote: > On 7/26/07, Alessandro Fiorenzi <a.fiorenzi@xxxxxxxxxxxx> wrote: >> RewriteRule ^/urlpath(.*) https://site.org/ >> >> work fine. but if in my browser I write /urlpath in hex is: >> %2f%75%72%6c%70%61%74%68%a does the rewrite rule match or not? > > My guess is that mod_rewrite will canonicalize the URL so you will get > a match. But watch out, since apache will reject any request with %2f > unless you use the AllowEncodedSlash directive. (And I'm not even sure > if a request without a leading slash is legal.) Not only that, but %2F != "/" Yes, %2F will translate to a '/' but not for purposes of separating URI components. In English, an example is that a sentence ends in period. Just because an ellipses ... the three dots ... happen to be periods, doesn't mean they end a sentence where an ellipses occurs. Consider a server that creates an ASCII-95 (printable) session ID. If the server decomposed %2F before passing these through as part of the path, the remote server would be unable to find it's session tag anymore. Bill --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|