Re: Unresolved subdomain linls

Kamil Tekiela <[email protected]> Thu, 1 Jan 2026 21:49:15 +0000
Newsgroups gmane.comp.php.documentation.general
Message-ID <CAGBsUrfXnyaptp1ZYFr__R49-N_8wrbJd57rFCtr73fbPTLENQ@mail.gmail.com>
On Thu, 1 Jan 2026 at 21:09, Jordi Kroon <[email protected]> wrote:
>
> I found the link to lists.php.net at https://www.php.net/mailing-lists.ph=
p. Specifically below the "Mailing List Options H2=E2=80=9D (see https://gi=
thub.com/php/web-php/blob/master/mailing-lists.php#L363).
>
> We could remove the link, or we could create a redirect for it. The redir=
ect would be purely for convenience, so anyone managing their preferences c=
an simply follow it through to the subdomain the email originates from.
>
> If the outcome is to remove the link, I will create a PR for that.
> On 1 Jan 2026 at 8:27=E2=80=AFPM +0100, Kamil Tekiela <[email protected]=
om>, wrote:
>
> On Thu, 1 Jan 2026 at 18:41, Jordi Kroon <[email protected]> wrote:
>
>
> Hi there,
>
> Happy New Year.
>
> While reviewing HTTP links I spotted a few subdomains that do not
> resolve anymore for various reasons.
>
> Within the PHP.net mailing list page there is a link pointing
> lists.php.net. As this link is very relevant I would suggest redirecting
> it to the same page as the link is mentioned.
> https://www.php.net/mailing-lists.php
>
> Secondly there is a docs.php.net that is not relevant anymore. Which we
> could redirect to www.php.net for legacy purposed. For example; SO has
> links to the docs that we might not want to break
> (https://stackexchange.com/search?q=3Durl%3adocs.php.net).
>
> In my PR (https://github.com/php/web-php/pull/1731) I have changed those
> to www.php.net as they are compatible with the links on PHP.net itself.
>
> Looking forwards to your thoughts.
>
> -
> Jordi Kroon
>
>
> It would be nice if you shared some context. Where did you find a link
> to lists.php.net?
>
> I was not familiar with docs.php.net but web archive opens the same
> page that we get on the root subdomain, so I think it's just one of
> the old obsolete subdomains that got decommissioned some time ago. In
> that case, replace it with php.net. Please do it in a separate PR.

I see, that's what you meant. No, the link shouldn't point to itself.
I wonder why that subdomain is no longer available. Perhaps someone on
this list knows the reason. I would leave it as it is now, because the
link points to the right place, but that place is gone. If it's never
going to come back again, then the paragraph needs to be rewritten to
remove the mention of it.