Re: tld.php.net

[email protected] ("ComunidadHosting")
Newsgroups php.mirrors
Message-ID <1416692848,[email protected]>
Thanks a lot, Hannes!

Finally, most of mirrors, including ours, are back to the official mirrors.php page. :)

If you allow me some feedback, and provided this can be fixed, I would like to point some minor issues and/or suggestions:

1. Minimum PHP version: According to the current /mirroring.php page, mirrors are required to use PHP 5.3.21 or greater. However, at status.php.net the orange status on the PHP column field is not displayed on mirrors using a version lower than 5.3.21 (for instance no1.php.net - 5.3.10), except by those using 5.3.3 (for instance pk1.php.net). As a suggestion, this might be standardized in a way in which the orange status is displayed when the mirror is not using the latest 5.3.x (or even 5.4.x) version available. :)

2. Stats: the output at http://status.php.net/ is declaring some mirrors as "does have statistics available", when they don't, or at least not available to visitors. For instance:

http://au1.php.net/stats/
http://dk1.php.net/stats/
http://in3.php.net/stats/ <- Password protected
http://sg3.php.net/ <- Password protected

Thanks Hannes.

By the way, we recently revamped our PHP mirrors. They are now featuring IPv6 (except by pa1.php.net), Stats and PHP 5.4.x. :)

All the best,

Jaime Echeverry
--
Administrativo
ComunidadHosting : Web hosting en tu idioma : http://www.comunidadhosting.com/

-----Mensaje original-----
De: "Hannes Magnusson" <[email protected]>
Enviado: Saturday, 22 November, 2014 2:06pm
Para: "Kaspars Foigts" <[email protected]>
CC: "PHP Mirrors List" <[email protected]>
Asunto: Re: tld.php.net

On Sat, Nov 22, 2014 at 2:39 AM, Kaspars Foigts <[email protected]> wrote:

> Hello!
>
> I started to receive complaints that lv.php.net is not accessible (no such
> DNS entry). lv1.php.net works, though. I checked other TLD.php.net (us,
> ee,
> lt, etc) and they appear to work.
>
>

Thanks for the headsup. This may have been our fault, we are detecting
incorrect rsycing as the file we are md5ing is no longer available :)

I've committed a likely fix for this, lets see what happens in couple of
hours.

-Hannes
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.