Conversation:
Notices
-
Chimo (chimo)'s status on Wednesday, 03-Feb-2016 14:23:33 EST
Chimo
@mmn Updated to PHP7 ~29days ago. I can't remember if it was an issue before that or not -
Chimo (chimo)'s status on Wednesday, 03-Feb-2016 14:01:09 EST
Chimo
@mmn question whenever you have a chance:
When I use this: https://code.chromic.org/chimo/gs-checkin/src/master/forms/checkin.php#L251
I get this: https://git.gnu.io/gnu/gnu-social/blob/nightly/extlib/HTTP/Request2.php#L377
Regarding this config value: https://git.gnu.io/gnu/gnu-social/blob/nightly/lib/httpclient.php#L120
Do you know why that would be? -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 03-Feb-2016 14:04:35 EST
MMN-o ✅⃠
@chimo It appears that HTTP_Request2 wants it to be called max_redirects (not max_redirs) -
Chimo (chimo)'s status on Wednesday, 03-Feb-2016 14:09:32 EST
Chimo
@mmn That's what I was thinking, now if I change 'max_redirs' to 'max_redirects' everywhere, I get the same error for 'ssl_SNI_enabled' from https://git.gnu.io/gnu/gnu-social/blob/nightly/lib/httpclient.php#L276
Which is the part that confuses me, because it looks like that part of the code hasn't been touched in years (so I assume it was working) O_o -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 03-Feb-2016 14:15:46 EST
MMN-o ✅⃠
@chimo Haha yeah, but maybe it's got to do with the backend no longer supporting those settings? Something that has been deprecated a long time and now finally removed? For example, "ssl_SNI_enabled" should've been enabled by default for ages by now I would assume. I'll see if I can find more info on it. -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 03-Feb-2016 14:18:07 EST
MMN-o ✅⃠
@chimo The SNI stuff appear to be SSL Context settings for PHP, see: https://secure.php.net/manual/en/context.ssl.php
Why they've started complaining now I don't know. Any version changes of software involved on your end? -
Chimo (chimo)'s status on Wednesday, 03-Feb-2016 14:53:12 EST
Chimo
@mmn oh wait, I don't get that error on my other instance with PHP7 running nightly:43abfe659b. Let me do a git pull and check again. -
Chimo (chimo)'s status on Wednesday, 03-Feb-2016 15:00:57 EST
Chimo
@mmn No errors. Hrm. Well the instance with problems is in a VM behind a proxy… Might mess some things up. Ignore me, sorry for the bother MMN-o ✅⃠ likes this. -
MMN-o ✅⃠ (mmn)'s status on Wednesday, 03-Feb-2016 15:33:14 EST
MMN-o ✅⃠
@chimo I like self-inflicted errors due to unique, weird administrative solutions. Except when I have to deal with it. :) Chimo likes this.
-