Repository navigation
Conversation
1. The www.php.net site is extremely slow on the first request, probably because it's rarely used and needs to "wake up" to serve the first request in a while, compared to just php.net which is always fast. Also changing it to HTTPS. 2. Now referencing HTTPS Zend website.
|
We should use secure.php.net if we are going to use https for php.net because of the certificates |
|
@KalleZ I saw that it redirects to secure.php.net, but I imagine that will change at some point? Just having https://php.net/ will account for the event you fully migrate everything to HTTPS without needing secure dot. |
|
Hi, I doubt that we will do that in any reasonable future because of the mirror certificates, so far no one have stepped up to solve it once and for all so until then I'm afraid we are stuck with just secure.php.net |
1 similar comment
|
Hi, I doubt that we will do that in any reasonable future because of the mirror certificates, so far no one have stepped up to solve it once and for all so until then I'm afraid we are stuck with just secure.php.net |
|
@KalleZ Ok then. I have changed it. |
|
I have an open PR for this already #3069 |
|
@carusogabriel I just checked yours and it does not include changes this one does. Do you want to add them and then I will just close this? |
|
Please close it, I'll update that one 👍 |
The www.php.net site is extremely slow on the first request, probably because it's rarely used and needs to "wake up" to serve the first request in a while, compared to just php.net which is always fast. Also changing it to HTTPS.
Now referencing HTTPS Zend website.