From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin@linuxfoundation.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS54825 139.178.80.0/21
X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,
	SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.6
Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id D7EAA1F5CB
	for <meta@public-inbox.org>; Tue, 10 Sep 2024 14:05:09 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=TYLF4OOa;
	dkim-atps=neutral
Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58])
	by dfw.source.kernel.org (Postfix) with ESMTP id 108125C0080;
	Tue, 10 Sep 2024 14:05:05 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1A28EC4CEC3;
	Tue, 10 Sep 2024 14:05:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
	s=korg; t=1725977108;
	bh=GQV84ERqnPJlIXw1hmoSP+Y/cLvg6qD9KTAN8rGsr3w=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=TYLF4OOaXCpazD+fhDF8qrXI7b7Ko9suAdRxq6tnH8FXZtlSRtzGq9UYukeOq1p5h
	 T3D+2oyHk9vp5uc/m8KssSPOoV3KuPEHg7xgknnHgqgFqGAGA25ndJWWqpciIGu0Y9
	 zPlI0wFTymZRPLl5Zpail91ZxkApJNNAdoYT9V68=
Date: Tue, 10 Sep 2024 10:05:06 -0400
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] view: fix x-post links for relative urls
Message-ID: <20240910-strong-rainbow-warthog-d6fe69@lemur>
References: <20240909-muskox-of-illegal-engineering-dadeda@lemur>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20240909-muskox-of-illegal-engineering-dadeda@lemur>
List-Id: <meta.public-inbox.org>

On Tue, Sep 10, 2024 at 12:40:48AM GMT, Eric Wong wrote:
> We need to make correct relative URL paths for users configuring
> publicinbox.$NAME.url as relative URL paths (e.g. matching the
> inbox `$NAME').
> 
> Users of protocol-relative (e.g. `//$HOST/$NAME') and absolute URIs
> (e.g `https://example.com/$NAME') were unaffected by this bug.
> Users relying on publicinbox.nameIsUrl and omitting
> publicinbox.*.url entries were also immune to this bug.

I've applied the patch, but I'm not sure it's quite what was intended as none
of the lists are linkified any more.

-K