Re: Bugzilla update and schedule for changeover

[Daniel Berlin <dberlin at dberlin dot org>]

On Tuesday, March 25, 2003, at 11:36  AM, Daniel Berlin wrote:

> On Tuesday, March 25, 2003, at 06:25  AM, Gerald Pfeifer wrote:
>
> > [ gcc-patches -> gcc ]
> >
> > On Mon, 24 Mar 2003, Daniel Berlin wrote:
> > > > although the simple case of links to a PR should also get redirected
> > > > smoothly),
> > > Auto-rewrite like that is an apache config issue that i have no  
> > > control
> > > over.
> >
> > Hmm, well, but before we can consider switching we really need some
> > to keep those links to  http://gcc.gnu.org/cgi-bin/gnatsweb.pl...
> > working properly that are spread all over mailing archives, mails
> > to individuals,...
> >
> > Does Bugzilla provide some forwarder, by any chance?
>
> Nope, but it doesn't need to.
> You *can* do this sort of thing pretty easily.
> It's a simple application of mod_rewrite.
> I just don't have *access* to the apache config files to set it up.
> Understand?
>
> You should be able to add something like
> RewriteEngine on
> RewriteRule ^/cgi-bin/gnatsweb.pl(.*)cmd=view(.*)pr=(\d+)(.*)   
> /bugzilla/show_bug.cgi?id=$3

Here's a tested rewrite rule:
RewriteCond %{QUERY_STRING}     .*cmd=view.*pr=(\d+)
RewriteRule ^.*gnatsweb.pl.*  /bugzilla/show_bug.cgi?id=%1



Tested on URL's of the following form:
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
trail&pr=7223

(with gcc.gnu.org replaced with dberlin.org).

This will now show bugzilla bug 7223
> To the apache config file, and make sure mod_rewrite is loaded.
>
> However, there is no easy way to *test* this rewrite without redirect  
> of all of the accesses occurring.
>
>
>
> > Gerald
> > --
> > Gerald "Jerry"   pfeifer at dbai dot tuwien dot ac dot at    
> > http://www.pfeifer.com/gerald/