Re: Unresolved subdomain linls
[email protected] (Jordi Kroon) Thu, 1 Jan 2026 22:09:32 +0100
| Newsgroups | php.doc |
|---|---|
| Message-ID | <9a9b0f20-0a34-4db2-8300-fc5e72bc1459@Spark> |
--6956e291_62bbd95a_1db3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I found the link to lists.php.net at https://www.php.net/mailing-lists.ph= p. Specifically below the =22Mailing List Options H2=E2=80=9D (see=C2=A0h= ttps://github.com/php/web-php/blob/master/mailing-lists.php=23L363). 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= can 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 <tekiela246=40gmail= .com>, wrote: > On Thu, 1 Jan 2026 at 18:41, Jordi Kroon <jordikroon=40me.com> 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 redirect= ing > > 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. =46or example; SO = has > > links to the docs that we might not want to break > > (https://stackexchange.com/search=3Fq=3Durl%3adocs.php.net). > > > > In my PR (https://github.com/php/web-php/pull/1731) I have changed th= ose > > to www.php.net as they are compatible with the links on PHP.net itsel= f. > > > > 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=3F > > 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. --6956e291_62bbd95a_1db3 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <html xmlns=3D=22http://www.w3.org/1999/xhtml=22> <head> <title></title> </head> <body> <div name=3D=22messageBodySection=22> <div dir=3D=22auto=22>I found the link to lists.php.net at https://www.ph= p.net/mailing-lists.php. Specifically below the =22Mailing List Options H= 2=E2=80=9D (see&=23160;<a href=3D=22https://github.com/php/web-php/blob/m= aster/mailing-lists.php=23L363=22 target=3D=22=5Fblank=22>https://github.= com/php/web-php/blob/master/mailing-lists.php=23L363</a>).<br /> <br /> 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= can simply follow it through to the subdomain the email originates from.= <br /> <br /> If the outcome is to remove the link, I will create a PR for that.</div> </div> <div name=3D=22messageReplySection=22>On 1 Jan 2026 at 8:27=E2=80=AFPM +0= 100, Kamil Tekiela <tekiela246=40gmail.com>, wrote:<br /> <blockquote type=3D=22cite=22 style=3D=22border-left-color: grey; border-= left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left:= 10px;=22>On Thu, 1 Jan 2026 at 18:41, Jordi Kroon <jordikroon=40me.co= m> wrote:<br /> <blockquote type=3D=22cite=22><br /> Hi there,<br /> <br /> Happy New Year.<br /> <br /> While reviewing HTTP links I spotted a few subdomains that do not<br /> resolve anymore for various reasons.<br /> <br /> Within the PHP.net mailing list page there is a link pointing<br /> lists.php.net. As this link is very relevant I would suggest redirecting<= br /> it to the same page as the link is mentioned.<br /> https://www.php.net/mailing-lists.php<br /> <br /> Secondly there is a docs.php.net that is not relevant anymore. Which we<b= r /> could redirect to www.php.net for legacy purposed. =46or example; SO has<= br /> links to the docs that we might not want to break<br /> (https://stackexchange.com/search=3Fq=3Durl%3adocs.php.net).<br /> <br /> In my PR (https://github.com/php/web-php/pull/1731) I have changed those<= br /> to www.php.net as they are compatible with the links on PHP.net itself.<b= r /> <br /> Looking forwards to your thoughts.<br /> <br /> -<br /> Jordi Kroon<br /></blockquote> <br /> It would be nice if you shared some context. Where did you find a link<br= /> to lists.php.net=3F<br /> <br /> I was not familiar with docs.php.net but web archive opens the same<br />= page that we get on the root subdomain, so I think it's just one of<br />= the old obsolete subdomains that got decommissioned some time ago. In<br = /> that case, replace it with php.net. Please do it in a separate PR.<br /><= /blockquote> </div> </body> </html> --6956e291_62bbd95a_1db3--