Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EAS autodiscover does not work for Samsung Galaxy S7 #34

Closed
wrosenauer opened this issue Mar 9, 2017 · 1 comment
Closed

EAS autodiscover does not work for Samsung Galaxy S7 #34

wrosenauer opened this issue Mar 9, 2017 · 1 comment

Comments

@wrosenauer
Copy link

(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.:
/usr/lib/automx/automx_wsgi.py

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.

And last but not least it seems to work fine with an iOS device so there is some client difference causing this behaviour. I could imagine the only thing required is to make the wsgi capable to work with chunked?

@MKuzma
Copy link

MKuzma commented Dec 13, 2017

Same error if Outlook 2016 tries to run autodiscovery, it tries to reveal autodiscover.xml but it isn't using any parameter, especially no "emailaddress" and get HTTP/500 because of the script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants