Today papyon based clients stopped working: aMSN2, emesene2, and telepathy. Any attempt to connect causes this error: [16:26:13 ERROR papyon.gnet.HTTP] Received error code 500 (Internal Server Error) from contacts.msn.com:80 [16:26:13 WARNING papyon.service] Transport Error :500 Non-papyon-based clients still work.
I change server from "contacts.msn.com" to "omega.contacts.msn.com" and it works for me. (on emesene2)
(In reply to comment #1) > I change server from "contacts.msn.com" to "omega.contacts.msn.com" and it > works for me. (on emesene2) It doesn't for me
(In reply to comment #2) > It doesn't for me neither for me (I tried some hours ago)
Hi, Found the bug and fixed. It should get committed and released soon. In the meantime, to fix it, apply this patch on papyon (in something like /usr/lib/python2.6/site-packages/papyon) and it should fix it : diff --git a/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py b/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py index 73c1127..42d7497 100644 --- a/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py +++ b/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py @@ -21,7 +21,7 @@ import xml.sax.saxutils as xml class LiveService(object): - CONTACTS = ("contacts.msn.com", "?fs=1&id=24000&kv=7&rn=93S9SWWw&tw=0&ver=2.1.6000.1") + CONTACTS = ("contacts.msn.com", "MBI") MESSENGER = ("messenger.msn.com", "?id=507") MESSENGER_CLEAR = ("messengerclear.live.com", "MBI_KEY_OLD") MESSENGER_SECURE = ("messengersecure.live.com", "MBI_SSL") p.s: Changing it to use the omega server won't help...
*** Bug 31010 has been marked as a duplicate of this bug. ***
Created attachment 39599 [details] [review] Patch to fix connection issues Adding a proper patch file rather than a badly-formated copy/paste.
*** Bug 31015 has been marked as a duplicate of this bug. ***
Path work fine for my
I confirm, the patch does fix the issue.
Fixed in papyon 0.5.2
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.