From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason at zx2c4.com (Jason A. Donenfeld)
Date: Wed, 8 Jan 2014 17:31:24 +0100
Subject: Relative URL for Atom feed announcement
In-Reply-To: <52CD799D.1030602@nachtgeist.net>
References: <52997E15.3020602@nachtgeist.net>
 <CAHmME9qC8Z6Bozjy7EMFGaP-V+aHjr+ZMjbyumHjTmfYpZqAsA@mail.gmail.com>
 <52CD799D.1030602@nachtgeist.net>
Message-ID: <CAHmME9qDiWMV4-_Mb8hBcXq-p7DJOcQE-MjCx5ZvdnsjJ47Xhg@mail.gmail.com>

On Wed, Jan 8, 2014 at 5:15 PM, Daniel Reichelt <nl at nachtgeist.net> wrote:
> The issue is not with the browser, the URL gets created wrongly by cgit
> due to my reverse-proxy setup. (A plain wget to external vhost also
> returns the full-qualified http://localhost:446/.... URL)

What I mean to say is that your patch proposes using a relative href
instead of an absolute one. I was hoping you could check to see
whether or not a relative href in the link meta tag causes problems in
browsers, before I merge this.