I think what you want to do to fix this is add a carat (^) before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if /mailman occurs at the beginning of
the string.
Personally, I use a little more inclusive regular
Just in case anyone was actually thinking of using that regexp I sent,
my limited knowledge tells me that this would be a slightly better
incarnation:
RewriteRule ^/(mailman[/]{0,1}){0,1}$ /mailman/listinfo [L,R]
Greg
On Saturday, January 18, 2003, at 09:46 AM, Greg Westin wrote:
I
At 14:46 18/01/2003, Greg Westin wrote:
I think what you want to do to fix this is add a carat (^) before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if /mailman occurs at the beginning of
the string.
Personally, I use a
I don't know what the I or | or whatever that is does - I assume it
does the same thing as {0,1}. But the important difference between the
rule I use:
RewriteRule ^/(mailman[/]{0,1}){0,1}$/mailman/listinfo [L,R]
and the ones you suggested is that mine also redirects requests for /
to
I know this is a simple question but I don't have the knowledge to
figure it out.
I am running RedHat 8.0 and which came with Mailman 2.0.13. It
suggests adding the following to the httpd.conf file:
# Uncomment the following line, replacing www.example.com with your server's
# name, to
