Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99989 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48320 invoked from network); 21 Jul 2017 08:47:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2017 08:47:43 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:22447] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/B1-02884-CAFB1795 for ; Fri, 21 Jul 2017 04:47:41 -0400 Message-ID: <4B.B1.02884.CAFB1795@pb1.pair.com> To: internals@lists.php.net References: In-Reply-To: Date: Fri, 21 Jul 2017 09:47:35 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] php.net website From: TonyMarston@hotmail.com ("Tony Marston") "Niklas Keller" wrote in message news:CANUQDCjB9UY8jTmmp43bQAW_9xJnoMbREN1zOQh1LubTfO4C-w@mail.gmail.com... > >> >> On Wed, Jul 19, 2017 at 1:07 PM, Mathias Grimm >> wrote: >> > I was briefly asking Sara about it and as she pointed out it is likely >> > a >> > big project but I think we can do something about it. >> > >> One thing I should have mentioned on twitter was: >> https://wiki.php.net/web/mirror >> >> That'll get you a locally running web-php instance though it's not >> ideal for iterative development against the git repo without some >> massaging. >> >> As to the actual hosts: There are (I believe) two hosts actually >> administered by @php.net folk: us1.php.net and us2.php.net, others >> (AIUI) are run by third parties and not under our control. The PHP >> version on these hosts is, comically, not the lastest-and-greatest. >> I'm fairly confident it's not even consistently 7.0+ so whatever you >> write needs to take that into account (particularly given the status >> of third-party mirrors). >> > >We should really change that and fully move to HTTPS. > >Regards, Niklas Why on earth should you need to use HTTPS for a website that does not deal with personal information? Nothing on that website can possibly be classed as "sensitive" so what would be the point? -- Tony Marston