Hi Christian,
i tried it, but it doesn't change anything.
I don't have a running installation to test, but i assume the following
curl command does nearly the same as my phone trying to connect. It
would be interesting how the response is on a working sogo.
It doesn't look like nginx is the problem. Could it be a problem with
sql auth instead of ldap?
curl -X OPTIONS -H "MS-ASProtocolVersion: 2.5" -u simon:pass
"http://localhost:20000/SOGo/Microsoft-Server-ActiveSync?User=simon&DeviceId=id&DeviceType=WP8";
-i
HTTP/1.1 200 OK
Sogo-Request-Duration: 0.059894
Content-Type: text/plain
Allow: GET, HEAD, POST, OPTIONS, MKCOL, MKCALENDAR, DELETE, PUT, LOCK,
UNLOCK, COPY, MOVE, REPORT, PROPFIND, SEARCH
Content-Length: 0
DAV: 1, 2
Simon
On 06/04/2015 08:20 PM, Christian M. Jensen wrote:
Hi Simon
have you tried
adding this to the config,
server {
.....
proxy_http_version 1.1;
proxy_set_header Connection "";
.....
}
also i'm not sure, but i dont think ssl stapling works without
'ssl_trusted_certificate', maby i'm wrong
Regards
Christian Jensen
On 04-06-2015 18:23, Simon Dieterle wrote:
Hi Christian,
i used the all the nginx.confs containting ActiveSync i found. But
right now this one is the one i use to test.
http://pastebin.com/BtwFrqvh
As i'm not interested in having a webinterface i don't mind the other
rules being wrong.
I don't understand why i get a response from SOGo but it does not
contain the AS version.
I also tried a sogo docker container which gave my the same behaviour.
Simon
On 06/04/2015 04:29 PM, Christian M. Jensen wrote:
hi.
what is your current nginx config?
i had to add 'proxy_set_header Connection "";' to my config in order to
get it running
Regards
Christian Jensen
On 03-06-2015 18:07, smnd...@openmailbox.org wrote:
Hi,
i compiled sogo 2.3.0 and everything is working as expected, except
active
sync.
I used the following rule in nginx
location ^~ /Microsoft-Server-ActiveSync {
proxy_pass
http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync
proxy_redirect
http://127.0.0.1:20000/Microsoft-Server-ActiveSync /;
}
I tried Microsofts Connectivity Tool and that's the result:
Testing HTTP Authentication Methods for URL
https://torment.simondieterle.net/Microsoft-Server-ActiveSync/.
The HTTP authentication test failed.
Additional Details
A 401 error was received from the server, but no authentication
methods are
supported.
HTTP Response Headers:
Connection: keep-alive
Keep-Alive: timeout=20
Sogo-Request-Duration: 0.000941
Content-Length: 0
Content-Type: text/plain
Date: Wed, 03 Jun 2015 15:35:56 GMT
Server: nginx/1.7.6
WWW-Authenticate: basic realm="SOGo"
Elapsed Time: 381 ms.
I also tried it from a WP8.1 Phone. It gives me an error about a wrong
server
versionen. I fired up wireshark on lo port 2000 and that's the output.
OPTIONS /SOGo/Microsoft-Server-ActiveSync?
User=simon&DeviceId=deviceid&DeviceType=WP8 HTTP/1.0
Host: 127.0.0.1:20000
Connection: close
Cache-Control: no-cache
Pragma: no-cache
Authorization: Basic b64stuff==
User-Agent: MSFT-WP/8.10.14219
MS-ASProtocolVersion: 2.5
HTTP/1.1 200 OK
Sogo-Request-Duration: 0.057482
Content-Type: text/plain
Allow: GET, HEAD, POST, OPTIONS, MKCOL, MKCALENDAR, DELETE, PUT, LOCK,
UNLOCK,
COPY, MOVE, REPORT, PROPFIND, SEARCH
Content-Length: 0
DAV: 1, 2
I assume the problem is that there are no MS-XXX headers in the
response,
which throws of the WP client.
I don't know where the problem could be, the proxying is working (i
assume)
because there is a Sogo- header in the response.
Can anyone point me anywhere? I tried 5 different nginx configs,
nothing
works.
--
users@sogo.nu
https://inverse.ca/sogo/lists
