EAS autodiscover

Wolfgang Rosenauer wolfgang at rosenauer.org
Thu Mar 2 09:21:19 CET 2017


(first as information I'm currently using the 0.10.2 tag as latest I
couldn't get to work (reported on github)).

I basically got everything set up and working but EAS.

With automx-test it seems to work but tried it with my Samsung device
and hit different issues:

the autodiscover request was answered with a 411 which apparently means
that Apache implied a chunked request.
Apache error log:
Received request requiring chunked transfer encoding, but optional
support for chunked transfer encoding has not been enabled.:

Apache access log:
[02/Mar/2017:09:06:45 +0100] "POST /autodiscover/autodiscover.xml
HTTP/1.1" 411 921
[02/Mar/2017:09:06:46 +0100] "GET /autodiscover/autodiscover.xml
HTTP/1.1" 500 - "-" "Android-SAMSUNG-SM-G930F/101.60001"

So the device seems to find the error with POST and tries a GET but
without any parameter which again yields into a 500 because automx
currently always requires a parameter.

All the above is not written to the automx debug log btw.

then I enabled WSGIChunkedRequest On to possibly get around the 411
which seemed to workaround the 411 but then again it seems to
immediately run also into a 500 for the POST request.

I currently do not have any packet level protocols for that but I'm
wondering if the Samsung EAS autodiscover is doing something strange or
if there is something else wrong in my setup.
Does it ring a bell to anyone?

(I do not have other EAS devices to test atm.)


More information about the automx-users mailing list