Combining the best of mod_rewrite and mod_proxy

I have a weird situation that I'm migrating a site that was using
WebSphere for a backend to using Resin. We have a requirement that
sessions be persistent to the app server, and we've done this thus far
by using ProxyPassMatch <blah> balancer://<blah>
stickysession=JSESSIONID and specifying the route to the backend app
server in the proxy definition.

I now have a requirement (or desire, I should say) for
case-insensitive matching of the URI to be passed through to the app
layer. I know that I can use mod_rewrite for this, using [NC] at the
end of the RewriteCond line that looks at the URI. However, how do I
get it to remain persistent to the app server in this setup?

------------------------------------------------------------ ---------
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 [at] httpd.apache.org
" from the digest: users-digest-unsubscribe [at] httpd.apache.org
For additional commands, e-mail: users-help [at] httpd.apache.org
Jon Stanley [ Di, 02 Februar 2010 23:32 ] [ ID #2031058 ]

RE: Combining the best of mod_rewrite and mod_proxy

It seems that coercing all your URLs to lower case is one option. This
is a bit brute-force, and assumes that you have no valid upper-case
URLs! That said, perhaps you could add a rule as follows:

RewriteMap lower int:tolower
RewriteRule ^/(.*) /${lower:$1}

--Pete

-----Original Message-----
From: Jon Stanley [mailto:jonstanley [at] gmail.com]
Sent: Tuesday, February 02, 2010 5:33 PM
To: users [at] httpd.apache.org
Subject: [users [at] httpd] Combining the best of mod_rewrite and mod_proxy

I have a weird situation that I'm migrating a site that was using
WebSphere for a backend to using Resin. We have a requirement that
sessions be persistent to the app server, and we've done this thus far
by using ProxyPassMatch <blah> balancer://<blah>
stickysession=3DJSESSIONID and specifying the route to the backend app
server in the proxy definition.

I now have a requirement (or desire, I should say) for case-insensitive
matching of the URI to be passed through to the app layer. I know that
I can use mod_rewrite for this, using [NC] at the end of the RewriteCond
line that looks at the URI. However, how do I get it to remain
persistent to the app server in this setup?

------------------------------------------------------------ ---------
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 [at] httpd.apache.org
" from the digest: users-digest-unsubscribe [at] httpd.apache.org
For additional commands, e-mail: users-help [at] httpd.apache.org


------------------------------------------------------------ ---------
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 [at] httpd.apache.org
" from the digest: users-digest-unsubscribe [at] httpd.apache.org
For additional commands, e-mail: users-help [at] httpd.apache.org
pthomas [ Di, 02 Februar 2010 23:46 ] [ ID #2031059 ]
Webserver » gmane.comp.apache.user » Combining the best of mod_rewrite and mod_proxy

Vorheriges Thema: Inaccuracy in mod_ssl docs
Nächstes Thema: Apache server configuration help required centos 5/3