ssl error : WebSub push tested again and again (seems)
If an user goes in 404 : 30 day after we don't try to send WebSub. But if there are a ssl error, then before header : it's seems to try again and again.
2017-06-15 14:31:07 LOG_ERR: [ostatus.shnoulle.net:queuedaemon.php:14184] HTTPClient: HTTP POST https://s.a80.fr/main/push/callback/5 - Unable to connect to ssl://s.a80.fr:443. Error: stream_socket_client(): unable to connect to ssl://s.a80.fr:443 (Unknown error) stream_socket_client(): Failed to enable crypto stream_socket_client(): Peer certificate CN=`belar.gsill.net' did not match expected CN=`s.a80.fr' 2017-06-15 14:31:07 LOG_ERR: [ostatus.shnoulle.net:queuedaemon.php:14184] Failed WebSub push to https://s.a80.fr/main/push/callback/5 for https://ostatus.shnoulle.net/api/statuses/user_timeline/1.atom (Exception): HTTP request failed without response to URL: 'https://s.a80.fr/main/push/callback/5'; discarding
%YAML 1.1 --- # shnoullenet_social.ostatus_profile - uri: "https://s.a80.fr/user/1" profile_id: 46658 feeduri: "https://s.a80.fr/api/statuses/user_timeline/1.atom" salmonuri: "https://s.a80.fr/main/salmon/user/1" avatar: "https://s.a80.fr/avatar/1-96-20170410205018.jpeg" created: "2017-04-11 09:20:33" modified: "2017-04-11 09:20:33" ...
Maybe something i done wrong ?
The 30 day thing is that the subscription ends then. If there are lingering subscriptions in the queue, they may still be retried (though I think they should be discarded on an exception?)
Either way, I have recently added an incremental count for errors on outgoing WebSub/PuSH, so the amount of errors for a certain callback can be quantified. That might help in the future to make this more intelligent.