rssLink RSS for all categories
 
icon_orange
icon_green
icon_red
icon_orange
icon_red
icon_green
icon_green
icon_orange
icon_red
icon_red
icon_green
icon_green
icon_green
icon_blue
icon_orange
icon_red
icon_green
icon_blue
icon_red
icon_red
icon_green
icon_red
icon_green
icon_blue
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_red
icon_green
 

FS#22251 — HTTPS call from website itself or cron / Appels HTTPS depuis son site ou un cron

Attached to Project— Web Hosting / CloudDB
Maintenance
All web clusters
CLOSED
100%
Since the HTTPS deployment, it cannot be possible to call a link from their site with https using curl (PHP), or calling their website in HTTPS from a cron. The standard error message received is "cURL error 35: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol"

A workaround was to call http://myweb.site:443 instead of https://myweb.site.

We will deploy a solution to do https call working. But, in this case, the workaround will not work anymore. We planned to deploy it in January. We will add the deployment planning soon in this task, and on community.ovh.com and on web@ml.ovh.net mailing list (send an email to web-subscribe@ml.ovh.net to subscribe).

----------
Depuis le déploiement de HTTPS, il n'est pas possible d'appeler un lien de son propre site en HTTPS en utilisant curl (PHP), ou en appelant son propre site en HTTPS depuis un cron. L'erreur standard dans ce cas est "cURL error 35: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol".

Une solution était d'appeler http://monsite.web:443 à la place de https://monsite.web.

Nous allons déployer une solution qui va rendre le HTTPS fonctionnel. Cependant, avec cette solution, le moyen détourné ne fonctionnera plus. Nous prévoyons de le déployer en janvier. Le planning du déploiement sera ajouté dans cette tâche prochainement, sur community.ovh.com et sur la mailing list web@ml.ovh.net (envoyez un email à web-subscribe@ml.ovh.net pour vous inscrire).
Date:  Thursday, 09 February 2017, 08:29AM
Reason for closing:  Done
Comment by OVH - Monday, 23 January 2017, 15:38PM

Here is the deployment planning.

2017-01-30: cluster012
2017-01-31: cluster014
2017-02-01: cluster017 & cluster021
2017-02-02: cluster002 & cluster005
2017-02-06: cluster003 & cluster006
2017-02-07: cluster007 & cluster010
2017-02-08: cluster011 & cluster013
2017-02-09: cluster015 & cluster020

Of course, this planning could changed in case of unplanned issue.


Comment by OVH - Monday, 30 January 2017, 14:08PM

Done on cluster012 / 1000gp since 7.00 am UTC+1


Comment by OVH - Tuesday, 31 January 2017, 09:12AM

Done on cluster014 since 8.00 am UTC+1


Comment by OVH - Wednesday, 01 February 2017, 09:20AM

Done on cluster017 since 8:00 am UTC+1


Comment by OVH - Wednesday, 01 February 2017, 15:45PM

Done on cluster021 since 3:30 pm UTC+1


Comment by OVH - Thursday, 02 February 2017, 07:43AM

Done on cluster005 since 7:40 am UTC+1


Comment by OVH - Thursday, 02 February 2017, 08:06AM

Done on cluster002 since 8:00 am UTC+1


Comment by OVH - Friday, 03 February 2017, 07:44AM

3 days ahead :
Done on cluster003 and cluster006 since 7:40 am UTC+1


Comment by OVH - Wednesday, 08 February 2017, 11:19AM

Done on cluster007 / xxl since 11.15am UTC+0001


Comment by OVH - Wednesday, 08 February 2017, 11:46AM

Done on cluster010 / 60gp since 11.45am UTC+0001


Comment by OVH - Wednesday, 08 February 2017, 13:44PM

Done on cluster011 / 300gp since 1.28pm UTC+0001


Comment by OVH - Wednesday, 08 February 2017, 13:47PM

Done on cluster013 / 20gp since 1.47pm UTC+0001


Comment by OVH - Thursday, 09 February 2017, 07:27AM

Done on cluster015 / mp since 7.25am UTC+0001


Comment by OVH - Thursday, 09 February 2017, 08:29AM

Done on cluster020 since 8.28am UTC+0001