Attractive URLs? Anyone use Turbine + mod_rewrite? Almost there ...

[Scott Merritt <SM...@abilizer.com>]

I've been tearing my hair out trying to get mod_rewrite to fully work with
Turbine...  maybe I'm approaching things wrong (and maybe I should find a
mod_rewrite group, but I was hoping someone in here has already done it.)

 I have Turbine running like it comes as a stand alone server and I'm trying
to beautify the URLs using the Apache HTTP Server.  I've gotten the rules to
work, but the URL always changes in the browser after the rewriting is done.
Essentially the user is shown the rewritten URL.

I have in httpd.conf:

        RewriteEngine on
        RewriteLog "/usr/local/apache/logs/mysite.com-rewrite.log"
        RewriteLogLevel 9

        RewriteRule ^/(.*)$ http://mysite.com:8081/myapp/servlet/myapp/$1
[P]
        ProxyPass       / http://mysite.com
        ProxyPassReverse / http://mysite.com/

And when I hit http://mysite.com I end up getting
http://mysite.com:8081/myapp/servlet/myapp in my browser's address bar and
my logs look like:

62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
[www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) init rewrite engine
with requested uri /
62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
[www.mysite.com/sid#80dd864][rid#813d51c/initial] (3) applying pattern
'^/(.*)$' to uri '/'
622.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
[www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) rewrite / ->
http://mysite.com:8081/myapp/servlet/myapp/
62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
[www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) forcing
proxy-throughput with http://mysite.com:8081/myapp/servlet/myapp/
62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
[www.mysite.com/sid#80dd864][rid#813d51c/initial] (1) go-ahead with proxy
request proxy:http://mysite.com:8081/myapp/servlet/myapp/ [OK]

So...  it seems like it's sorta working.  Any ideas how to prevent it from
still showing the true URL to the user?  I thought it would use mod_proxy to
fetch the page itself and just pass the data to the end user.  Help!

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Attractive URLs? Anyone use Turbine + mod_rewrite? Almost there...

[Costas Stergiou <cs...@aias.gr>]

Why don't you use the mod_jk? It works fine!

----- Original Message -----
From: "Scott Merritt" <SM...@abilizer.com>
To: "'Turbine Users List'" <tu...@jakarta.apache.org>
Sent: Tuesday, November 27, 2001 8:59 PM
Subject: Attractive URLs? Anyone use Turbine + mod_rewrite? Almost there...


> I've been tearing my hair out trying to get mod_rewrite to fully work with
> Turbine...  maybe I'm approaching things wrong (and maybe I should find a
> mod_rewrite group, but I was hoping someone in here has already done it.)
>
>  I have Turbine running like it comes as a stand alone server and I'm
trying
> to beautify the URLs using the Apache HTTP Server.  I've gotten the rules
to
> work, but the URL always changes in the browser after the rewriting is
done.
> Essentially the user is shown the rewritten URL.
>
> I have in httpd.conf:
>
>         RewriteEngine on
>         RewriteLog "/usr/local/apache/logs/mysite.com-rewrite.log"
>         RewriteLogLevel 9
>
>         RewriteRule ^/(.*)$ http://mysite.com:8081/myapp/servlet/myapp/$1
> [P]
>         ProxyPass       / http://mysite.com
>         ProxyPassReverse / http://mysite.com/
>
> And when I hit http://mysite.com I end up getting
> http://mysite.com:8081/myapp/servlet/myapp in my browser's address bar and
> my logs look like:
>
> 62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
> [www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) init rewrite engine
> with requested uri /
> 62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
> [www.mysite.com/sid#80dd864][rid#813d51c/initial] (3) applying pattern
> '^/(.*)$' to uri '/'
> 622.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
> [www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) rewrite / ->
> http://mysite.com:8081/myapp/servlet/myapp/
> 62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
> [www.mysite.com/sid#80dd864][rid#813d51c/initial] (2) forcing
> proxy-throughput with http://mysite.com:8081/myapp/servlet/myapp/
> 62.126.164.218 - - [27/Nov/2001:10:42:58 -0800]
> [www.mysite.com/sid#80dd864][rid#813d51c/initial] (1) go-ahead with proxy
> request proxy:http://mysite.com:8081/myapp/servlet/myapp/ [OK]
>
> So...  it seems like it's sorta working.  Any ideas how to prevent it from
> still showing the true URL to the user?  I thought it would use mod_proxy
to
> fetch the page itself and just pass the data to the end user.  Help!
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>