Protocol plugin for Office 365/Lync/OCS / Bugs / #240 Corrupted HTTP response crashes SIPE

Your web server responds with an illegal HTTP response to our EWS request:

15:35:17: (GLib): (15:35:17) sipe: sipmsg_parse_header(): Content-Length header not found
15:35:17: (Libpurple: sipe) sipmsg_parse_header(): Content-Length header not found
15:35:17: (GLib): (15:35:17) sipe: 
MESSAGE START <<<<<<<<<< HTTP - 2014-04-15T13:35:17.682409Z
HTTP/1.1 405 Access Denied
Server: GoAhead-Webs
Date: Tue May  1 22:51:54 2012
Pragma: no-cache
Cache-Control: no-cache
Content-Type: text/html

MESSAGE END <<<<<<<<<< HTTP - 2014-04-15T13:35:17.682409Z

Unfortunately the body is not empty and therefore the next HTTP buffer processing step contains junk:

15:35:17: (GLib): (15:35:17) sipe: 
MESSAGE START <<<<<<<<<< HTTP - 2014-04-15T13:35:17.682959Z
<html><head><title>Document Error: Access Denied</title></head>
        <body><h2>Access Error: Access Denied</h2>
        <p>Invalid or corrupted session detected. Please close your browser and login again</p></body></html>


MESSAGE END <<<<<<<<<< HTTP - 2014-04-15T13:35:17.682959Z

Somehow this seems to lead to a crash, but where exactly I haven't figure out yet.

Joe - 2014-04-15

Thanks for the very quick investigation and response.

It would be helpful if it can avoid the crash and provide a meaningful message (I understand that it is easy to ask than to get it done that way)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-15

As a workaround you can disable publishing of your calendar information in the account settings. As EWS is obviously not working for your account you will not experience a loss in functionality.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Joe - 2014-04-15

I did not exactly understand. Where to disable the publishing of calendar information? In my domain outlook account or in the adium or in my Mac.

If domain outlook account, I don't see the settings in that. Probably I should contact my administrator to disable that.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-15

sigh In the SIPE account settings.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-15

summary: Adium SIPE Crashes in Mac --> Corrupted HTTP response crashes SIPE

assigned_to: Stefan Becker
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-15

This should be fixed in commit 9df2685

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Joe - 2014-04-16

Disabling the calendar publishing helps. The Adium has been running without crash for the past 3 hours.. And thanks for the fix. When the next SIPE is release, I will take it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-16

Unfortunately I have been unable to reproduce the crash on Linux. Even valgrind doesn't show an illegal access without the fix. I can only assume that the crash is caused by some Adium, OpenSSL or Mac special circumstances.

I would really appreciate if you could compile git HEAD and confirm that the crash is gone. The build instructions can be found here.

As I have no other way to confirm this, I assume that it is fixed and close the bug.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Stefan Becker - 2014-04-16

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Corrupted HTTP response crashes SIPE

for Adium, Pidgin, Miranda and Telepathy IM Framework

Group

Searches

Help

#240 Corrupted HTTP response crashes SIPE

Related

Discussion