>From the mod_rewrite manual page:
> + 'nocase|NC' (no case)
> This makes the test case-insensitive, i.e., there is no difference between
> 'A-Z' and
> 'a-z' both in the expanded TestString and the CondPattern. This flag is
> effective only
> for comparisons between TestString and CondPattern. It has no effect on
> filesystem and
> subrequest checks.
If you want to convert the URL path to lowercase, the following directives will
convert the first element of the path to all lowercase characters while
preserving the rest of the path:
RewriteMap canonicalize int:tolower
RewriteRule /([^/]+)(.*) /${canonicalize:$1}$2
Another alternative for your [Ee]xchange problem:
RewriteCond $1 exchange [NC]
RewriteRule /([^/]+)(.*) http://10.41.63.12/exchange$2
[P]
ProxyPassReverse /exchange
http://10.41.63.12/exchange
Be aware that ProxyPass directives are evaluated BEFORE rewrite rules. AFAIK
you cannot rewrite and then have the rewritten URL ProxyPass'ed.
This will probably not solve your problem, but I hope it will at least give you
some leeds.
-ascs
________________________________
From: Gary W. Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 11:46 PM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Rewrite / reverse proxy question
<![endif]--> <![endif]-->
Unfortunately no, the sample didn't appear to work. I think that you gave me
another sample some time ago (/[Ee]xchange) which worked for the two cases but
there is a little more behind the scenes that we are worried about. A little
more detail on the rest of the problem. We have 25 share point portal service
instances that we are proxing as well as Exchange. They work just fine for the
most part. There are a set of complex legacy web pages that have hundreds of
links in upper and lower case. This is the problem that we are truly trying to
solve with case insensitivity.
So for that question, is there any way to force the case insensitivity for the
entire string when doing a RuleRewrite.
As for the SSL, I think we will just throw a second apache instance on a second
IP and then use that for SSL using a redirector. It's not an elegant solution
but it should solve the general problem.
________________________________
From: Axel-Stéphane SMORGRAV [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 8:17 AM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Rewrite / reverse proxy question
Does it work for you? If it does, leave it as it is. I do however suspect that
the example you saw was was some Perl stuff.
Anyway, what are you trying to achieve with that particular directive?
I guess that the SSL stuff you mentioned is you priority. It would be nice if
you gave sus omething more to work on.
Could you install Firefox/LiveHTTPHeaders, run your SSL scenario and post the
LiveHTTPHeader output? If you can't, your access logs from the SSL virtual host
would be the next best thing.
-ascs
________________________________
From: Gary W. Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 4:11 PM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Rewrite / reverse proxy question
<![endif]-->
I found it in a sample somewhere. I'm not a regexp guy so I basically use what
I can find. It's one of those things on my to do list but I haven't got to it
yet.
________________________________
From: Axel-Stéphane SMORGRAV [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 28, 2005 12:35 AM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Rewrite / reverse proxy question
Pardon my ignorance, but what is that tilde (~) stuff doing in the RewriteRule
??
RewriteRule ^/~/[Ee]xchange /exchange/ [R]
# This doesn't seem to work either
#RewriteRule ^/~/exchange/i /exchange/ [R]
---------------------------------------------------------------------
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]
