Protocol plugin for Office 365/Lync/OCS / Bugs / #259 HTML response to EWS autodiscover triggers libxml2 assert

Stefan Becker - 2014-07-10

You obviously ignored the pointer to read the FAQ. I'll re-open this bug when the required information is added to this report.

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

Stefan Becker - 2014-07-10

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

Fabrice Bacchella - 2014-07-10

Here it is.

2014-07-10 1.log

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

Stefan Becker - 2014-07-10

summary: Adium 1.5.10 continuously crash with version 1.18.2 --> HTML response to EWS autodiscover trigger libxml2 assert

status: closed-invalid --> accepted

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-07-10

Thanks for the debug log.

In your setup the last EWS HTTP request triggers a HTML response, which obviously triggers an assert in libxml2 when we are asking it to parse the reponse body as XML.

As a workaround you can disable "publish my calendar information" in the SIPE account settings. That will disable EWS autodiscover process to be triggered.

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

Stefan Becker - 2014-07-10

This should be fixed by git commit 1bb58b5.

@reporter: I need to you to compile SIPEAdiumPlugin from git HEAD, because I can't reproduce your error condition in my setup. Thank you.

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

Stefan Becker - 2014-07-10

summary: HTML response to EWS autodiscover trigger libxml2 assert --> HTML response to EWS autodiscover triggers libxml2 assert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Fabrice Bacchella - 2014-07-10

The workarounds works.

But not the patch.

The stack :
19:34:38: -[ESDebugController exceptionHandler:shouldLogException:mask:]:76: Exception raised: Uncaught system exception: signal 11
19:34:38: 0 Adium 0x00000001004d7e40 AILogBacktrace_impl + 54
1 Adium 0x000000010005f3cd Adium + 390093
2 ExceptionHandling 0x0000000100a909e2 -[NSExceptionHandler _handleException😷] + 168
3 ExceptionHandling 0x0000000100a907ba NSExceptionHandlerUncaughtSignalHandler + 35
4 libsystem_c.dylib 0x00007fff8b36f90a _sigtramp + 26
5 ??? 0x0000000000000105 0x0 + 261
6 libxml2.2.dylib 0x00007fff8a7269d2 __xmlRaiseError + 1453
7 libxml2.2.dylib 0x00007fff8a73c8a0 xmlFatalErrMsg + 162
8 libxml2.2.dylib 0x00007fff8a740253 xmlParsePITarget + 117
9 libxml2.2.dylib 0x00007fff8a7404c7 xmlParsePI + 210
10 libxml2.2.dylib 0x00007fff8a74922d xmlParseMisc + 93
11 libxml2.2.dylib 0x00007fff8a749543 xmlParseDocument + 753
12 libxml2.2.dylib 0x00007fff8a74d5ec xmlSAXUserParseMemory + 106

In the log :
POST /Autodiscover/Autodiscover.xml HTTP/1.1
Host: 3ds.com
User-Agent: Sipe/1.18.2
Accept: text/xml
Content-Length: 326
Content-Type: text/xml

But the server don't care :
HTTP/1.1 303 See Other
...
Location: https://3ds.com/404-not-found/
Content-Type: text/html

And after the repost :
POST /404-not-found/ HTTP/1.1
Host: 3ds.com
...
Accept: text/xml

And the response:
HTTP/1.1 200 OK
...
Content-Type: text/html

I know it's badly broken server. But I can't fix it :-(.

There is something else fishy.

In the log, i see :
POST /Autodiscover/Autodiscover.xml HTTP/1.1
Host: autodiscover.3ds.com
User-Agent: Sipe/1.18.2
Accept: text/xml
Content-Length: 326
Content-Type: text/xml

<autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006"> <request> <emailaddress>fabrice.bacchella@3ds.com</emailaddress> <acceptableresponseschema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a </acceptableresponseschema></request></autodiscover>

and :
POST /Autodiscover/Autodiscover.xml HTTP/1.1
Host: 3ds.com
User-Agent: Sipe/1.18.2
Accept: text/xml
Content-Length: 326
Content-Type: text/xml

<autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006"> <request> <emailaddress>fabrice.bacchella@3ds.com</emailaddress> <acceptableresponseschema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a </acceptableresponseschema></request></autodiscover>

Why some discovery is done on autodiscover.3ds.com (this one almost works) and on 3ds.com (this one is broken) ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Stefan Becker - 2014-07-10
  
  Why some discovery is done on autodiscover.3ds.com (this one almost works) and on 3ds.com (this one is broken) ?
  
  Because https://%s/Autodiscover/Autodiscover.xml is a fallback that is tried last, which some users needed in the past. See src/core/sipe-ews-autodiscover.c.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BTW: it seems the Mac OS X libxml2 seems to be too old or broken. When I create a fake EWS that responds with the HTML contents from your log, I see the following from the log (Fedora 20):

(20:52:36) sipe: XML parser error: Domain 1, code 64, level 3: XML declaration allowed only at the start of the document
(20:52:36) sipe: XML parser error: Domain 1, code 80, level 3: Double hyphen within comment
(20:52:36) sipe: XML parser error: Domain 1, code 68, level 3: xmlParseStartTag: invalid element name
(20:52:36) sipe: XML parser error: Domain 1, code 76, level 3: Opening and ending tag mismatch: link line 75 and head
(20:52:36) sipe: XML parser error: Domain 1, code 76, level 3: Opening and ending tag mismatch: img line 177 and a
(20:52:36) sipe: XML parser error: Domain 1, code 76, level 3: Opening and ending tag mismatch: a line 177 and div
(20:52:36) sipe: XML parser error: Domain 1, code 76, level 3: Opening and ending tag mismatch: img line 180 and a
(20:52:36) sipe: XML parser error: Domain 1, code 76, level 3: Opening and ending tag mismatch: a line 180 and div
(20:52:36) sipe: XML parser error: Domain 1, code 68, level 3: xmlParseEntityRef: no name
(20:52:36) sipe: XML parser error: Domain 1, code 68, level 3: xmlParseEntityRef: no name
...
(20:52:36) sipe: XML parser error: Domain 1, code 77, level 3: Premature end of data in tag meta line 74
(20:52:36) sipe: XML parser error: Domain 1, code 77, level 3: Premature end of data in tag head line 6
(20:52:36) sipe: XML parser error: Domain 1, code 77, level 3: Premature end of data in tag html line 5
(20:52:36) sipe: ucs_ews_autodiscover_cb: can't detect EWS URL, contact list operations will not work!

So libxml2 complains and returns a parse error instead of barfing.

Fabrice Bacchella - 2014-07-10

That's possible, I'm on 10.8.5, not 10.9.

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

Stefan Becker - 2014-07-10

Added an additional check on Content-Type in git commit 6061788

@reporter: please verify, thank you

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

Fabrice Bacchella - 2014-07-11

yes it works.

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

Stefan Becker - 2014-07-11

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

Stefan Becker - 2014-07-11

Thanks. CLOSING

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

HTML response to EWS autodiscover triggers libxml2 assert

for Adium, Pidgin, Miranda and Telepathy IM Framework

Group

Searches

Help

#259 HTML response to EWS autodiscover triggers libxml2 assert

Related

Discussion