Ah, spoke too soon. It was handling redirects and https, but not always redirects and https and POST. But if I simply reconfigure the script to hit the https: addresses from the beginning (meaning the server doesn't have to send any redirects at all), everything works fine. Dunno why I didn't try that at first. (In hindsight, dunno why I didn't do that years ago.)
I wrote: > That would be a good guess, but the script handles redirects and > https just fine -- or at least it did, when those changes went > into effect a month ago. It was working fine up until this past > Tuesday or Wednesday, when it stopped being able to log in. > > > Tyler Romeo wrote: > > My guess is either the script does not handle redirects, and is failing > > when the login page tries to redirect you to HTTPS, or your script doesn't > > handle HTTPS, and fails when redirected to the secure page. > > > >On Sat, Aug 31, 2013 at 6:48 AM, Bartosz DziewoÅski > ><matma....@gmail.com>wrote: > >> There is very little JavaScript on the login page. > >> > >> Is your script HTTPS-compliant? Logging in is now HTTPS-only since a few > >> days ago, attempting to access the login page via HTTP will redirect you to > >> HTTPS. > >> > >> -- > >> Matma Rex
_______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l