|
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:Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx] 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:gary@xxxxxxxxxxxxxxx] <![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:Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx] 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] |
|