patch for clientLogin issue
Matthew S Goldstein
austein at MIT.EDU
Fri Jan 15 11:05:40 EST 2010
Word is the AIM servers are going to be fixed to not insert the ":80" so
we should be fine just patching http -> https
Not sure I'll hear when they do it, but it sounded like it would happen
soon so if anybody wants to check in a day or two, it might work then.
(I'd do it myself, but I'll be doing a puzzle competetion all weekend)
On Thu, 14 Jan 2010, Paul Aurich wrote:
> Forgot to mention that Matthew said he was going to contact the AOL folks and see if they could fix this on their end.
> On Jan 14, 2010, at 15:32, Paul Aurich wrote:
>> Matthew Goldstein (austein on IRC) figured out why trying to use the startOSCARSession method was failing with a signature error when tried to use over SSL (which would work around the server complaining that we try to set useTLS=1 over http). In short, the signature needs to use the URL "https://api.oscar.aol.com:80/...", while still connecting to port 443.
>> I wasn't comfortable committing this because I'm concerned that it would just break again if the servers are fixed to use the correct URL in the signature generation (or rather, no port at all, as the online docs indicate).
>> Nevertheless, Matthew, thanks for figuring this out!
More information about the Devel