public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Bernhard Reutner-Fischer via Overseers <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
	Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
	aldot@gcc.gnu.org
Subject: Re: Web: inbox/gcc-bugs broken links (for all bugzilla mails)
Date: Mon, 17 Apr 2023 11:07:11 +0200	[thread overview]
Message-ID: <20230417090711.GI20056@gnu.wildebeest.org> (raw)
In-Reply-To: <20230414094553.5b3fb61c@nbbrfq>

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

      parent reply	other threads:[~2023-04-17  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 10:00 Bernhard Reutner-Fischer
2023-04-13 20:27 ` Frank Ch. Eigler
2023-04-14  7:45   ` Bernhard Reutner-Fischer
2023-04-14 15:04     ` Frank Ch. Eigler
2023-04-16 19:34       ` Bernhard Reutner-Fischer
2023-04-17  9:07     ` Mark Wielaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230417090711.GI20056@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=aldot@gcc.gnu.org \
    --cc=fche@elastic.org \
    --cc=overseers@sourceware.org \
    --cc=rep.dot.nop@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).