On 9/18/08, Stauffer, Robert G <[EMAIL PROTECTED]> wrote:
> Same thing happened: It serves up the correct page, but the browser URL
> is http://example.com/ instead of
> http://example.com/site/jazzd/pid/9.  And the second RewriteRule is
>  ignored:
>  Bob Stauffer

You may be confusing several different processes.
1. The browser sends a request.  If the URL for http://example.com/
should redirect to http://example.com/site/jazzd/pid/9, then you need
a redirect.  Only a redirect will change the browser's URL.
2. The server responds to a request.  If
http://example.com/site/jazzd/pid/9 should be served by
http://portal-dev:81/jahia/Jahia/site/jazzd/pid/9, then a RewriteRule
should add the "jahia/Jahia/".  RewriteRules do not affect the
browser, only how the server processes the request.
3. The page is sent to the browser.  Links on the page may include the
"jahia/Jahia/".  People following the links will see the
"jahia/Jahia/".  Fixing the links requires either changing the
application that created the page (often by configuring the root URL)
or using mod_proxy_html.  Rewriting links is obviously critical
functionality still not included in Apache httpd.  (My first Web
application included this functionality.)

Rewrite_Rules do not change browsers' URLs.  You need to use the
correct technology to create your solution.

solprovider

---------------------------------------------------------------------
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: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to