Web: inbox/gcc-bugs broken links (for all bugzilla mails)

Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Bernhard Reutner-Fischer]

Hi!

When i direct my browser to
 https://inbox.sourceware.org/gcc-bugs/
i get 404 for every link there.

ATM this renders to e.g.:
---8<---
[Bug fortran/66973] New: Incorrect resolution of generic interface with TYPE(C_PTR)
 2023-04-12 18:48 UTC  (2+ messages)
` [Bug fortran/66973] "
---8<---
source:
---8<---
<a
href="bug-66973-4@http.gcc.gnu.org%2Fbugzilla%2F/T/#t">[Bug fortran/66973] New: Incorrect resolution of generic interface with TYPE(C_PTR)</a>
 2023-04-12 18:48 UTC  (2+ messages)
` <a
href="bug-66973-4-10qXbFF8QB@http.gcc.gnu.org%2Fbugzilla%2F/T/#u">[Bug fortran/66973]</a> &#34;
---8<---

The first link yields a 404
  https://inbox.sourceware.org/gcc-bugs/bug-66973-4@http.gcc.gnu.org%2Fbugzilla%2F/T/#t
and the second link likewise returns 404
  https://inbox.sourceware.org/gcc-bugs/bug-101018-4-9OS85Mwt0G@http.gcc.gnu.org%2Fbugzilla%2F/T/#u

Instead of the 404, i would have hoped to see the contents
of something like
https://gcc.gnu.org/pipermail/gcc-bugs/2023-April/818551.html
for the first link
and for the second (probably) gcc.gnu.org/PR66973#c7

Note that this 404 seems to happen to all bugzilla mails, e.g. in
https://inbox.sourceware.org/overseers/
there is "[Bug Infrastructure/29619] New: Setup gitolite for projects"
which points to
https://inbox.sourceware.org/overseers/bug-29619-14326@http.sourceware.org%2Fbugzilla%2F/T/#t
which also gives a 404.

PS: Currently we have an URL rewrite for gcc.gnu.org/ for
    something like ^/PR([0-9]+) /bugzilla/show_bug.cgi?id=$1
    Could we please also support rewrites of lowercase "pr" for that's
    easier to type on virtual keyboards?

thanks!

Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Frank Ch. Eigler]

Hi -

> When i direct my browser to
>  https://inbox.sourceware.org/gcc-bugs/
> i get 404 for every link there.

Mark and I fixed this long-standing problem by tweaking the way
sourceware's httpd reverse-proxies to public-inbox.  Thanks for
the report!

- FChE

Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Bernhard Reutner-Fischer]

On Thu, 13 Apr 2023 16:27:04 -0400
"Frank Ch. Eigler" <fche@elastic.org> wrote:

> Hi -
> 
> > When i direct my browser to
> >  https://inbox.sourceware.org/gcc-bugs/
> > i get 404 for every link there.  
> 
> Mark and I fixed this long-standing problem by tweaking the way
> sourceware's httpd reverse-proxies to public-inbox.  Thanks for
> the report!

Many thanks for the speedy fix! I confirm they all work fine now.

> PS: Currently we have an URL rewrite for gcc.gnu.org/ for
>     something like ^/PR([0-9]+) /bugzilla/show_bug.cgi?id=$1
>     Could we please also support rewrites of lowercase "pr" for that's
>     easier to type on virtual keyboards?

Any chance you could also tweak the rewrite regex?
That would be marvellous :)

Thanks for your great support and cheers,

Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Frank Ch. Eigler]

Hi -

> > PS: Currently we have an URL rewrite for gcc.gnu.org/ for
> >     something like ^/PR([0-9]+) /bugzilla/show_bug.cgi?id=$1
> >     Could we please also support rewrites of lowercase "pr" for that's
> >     easier to type on virtual keyboards?
> 
> Any chance you could also tweak the rewrite regex?
> That would be marvellous :)

OK, all done.

(While in the vicinity, I nuked some ancient NYTPROF related env var
settings, which was related to perl script tracing to some /tmp file.)

- FChE

Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Bernhard Reutner-Fischer]

On 14 April 2023 17:04:05 CEST, "Frank Ch. Eigler" <fche@elastic.org> wrote:

>OK, all done.

Works like a charm.
Thanks!

Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)

[Mark Wielaard]

Hi,

On Fri, Apr 14, 2023 at 09:45:53AM +0200, Bernhard Reutner-Fischer via Overseers wrote:
> On Thu, 13 Apr 2023 16:27:04 -0400
> "Frank Ch. Eigler" <fche@elastic.org> wrote:
> > > When i direct my browser to
> > >  https://inbox.sourceware.org/gcc-bugs/
> > > i get 404 for every link there.  
> > 
> > Mark and I fixed this long-standing problem by tweaking the way
> > sourceware's httpd reverse-proxies to public-inbox.  Thanks for
> > the report!
> 
> Many thanks for the speedy fix! I confirm they all work fine now.

All praise should go to Frank who actually investigated and noticed
that locally, without a http proxy in front of public-inbox-httpd (it
runs as its own isolated user), things seemed to work fine.

So in case others are running public-inbox-httpd behind an Apache
proxy then you want to add nocanon to ProxyPass and set
AllowEncodedSlashes On

Cheers,

Mark