Bug #73813 [Com]: Access to php.net through a company firewall

Edit report at https://bugs.php.net/bug.php?id=73813&edit=1 ID: 73813 Comment by: levim@php.net Reported by: julien dot w dot dev at gmail dot com Summary: Access to php.net through a company firewall Status: Closed Type: Bug Package: Website problem Operating System: Linux Fedora 20, Windows 10 PHP Version: Irrelevant Assigned To: levim Block user comment: N Private report: N New Comment: Meh, I didn't know what the text of that quick option would be; but this is fixed on live websites. Previous Comments: ------------------------------------------------------------------------ [2017-01-16 04:44:16] levim@php.net Thank you for your bug report. This issue has already been fixed in the latest released version of PHP, which you can download at http://www.php.net/downloads.php ------------------------------------------------------------------------ [2017-01-16 04:42:51] krakjoe@php.net Assigning to you Levi, do as you think is best please. ------------------------------------------------------------------------ [2017-01-06 23:50:09] cmb@php.net > Anyone opposed to always serving a PNG or SVG? What about changing the attribute value from logo.php to logo.(png|svg)? If we want to serve dynamic content, we could rewrite the URL to point to an actual PHP script. Guess the firewall would be fine with this. ------------------------------------------------------------------------ [2016-12-28 17:10:05] levim@php.net Perhaps we can work towards https on everything; historically this would have been cost prohibitive but perhaps we could use Let's Encrypt. ------------------------------------------------------------------------ [2016-12-28 16:07:37] maggus dot staab at gmail dot com Souldnt php.net be https only (so redirect all unencrypted traffic to a encrypted equvialent)? That way firewalls also cannot mess with the contents.. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=73813 -- Edit this bug report at https://bugs.php.net/bug.php?id=73813&edit=1