This patch adds support for tor hidden-services, which allows you to host e.g. owncloud without the need for a dyndns service.
Davdroid will use a socks proxy (on 127.0.0.1:9050) to connect to a .onion address.
nginx HTTP/2 incompatible with okhttp (REFUSED_STREAM)
-
At the moment, we’re unable to reproduce this problem with our own server (nginx 1.10.0, built with OpenSSL 1.0.1p-freebsd 9 Jul 2015) and DAVdroid 1.0.8 on various devices (Fairphone 2 with Android 5, Samsung Note 10.1, Samsung S2).
Although HTTP/2 is enabled in nginx for the respective host (and used by browsers), DAVdroid (okhttp) won’t use HTTP/2 …
-
According to https://github.com/square/okhttp/issues/2543#issuecomment-220778843:
nginx attached a proposed patch on their issue tracker. I tested patch against OkHttp and it worked perfectly.
So I still don’t know whether this is a client library or server bug … my recommendation is to disable HTTP/2 everywhere where you can find it (e.g. nginx).
-
@rfc2822 It seems a client bug, because everything else works as expected.
-
@rfc2822 It seems a client bug, because everything else works as expected.
Thanks for your hint, but “seems” is not enough here. We have to know where this error comes from, and then we can fix or work around it.
-
Just upgraded my server from Debian 8 to Ubuntu 16.04 with nginx 1.10. When HTTP2 is enabled davdroid doesn’t work, when it’s disabled it starts to work again. So I don’t know where exactly is the problem but I would be glad to help if any kind of testing needs to be done.
-
According to https://github.com/square/okhttp/issues/2543#issuecomment-220831104, nginx has got a patch so that the default configuration will work with okhttp 3.2 (= DAVdroid 1.0.8) again. In my opinion, this would justify waiting and doing nothing until okhttp 3.3 is released, which will then be used in the next DAVdroid version.
-
nginx 1.11.0 has been released, and as far as I have understood it, in its default configuration there should be no more REFUSED_STREAM errors with okhttp. Can you please check?
-
@rfc2822 said in nginx HTTP/2 incompatible with okhttp (REFUSED_STREAM):
nginx 1.11.0 has been released, and as far as I have understood it, in its default configuration there should be no more REFUSED_STREAM errors with okhttp. Can you please check?
That’s a shame that they didn’t go with 1.10.1
I don’t think ubuntu will have it now. I have to compile from source. I will let you know. -
@rfc2822 said in nginx HTTP/2 incompatible with okhttp (REFUSED_STREAM):
nginx 1.11.0 has been released, and as far as I have understood it, in its default configuration there should be no more REFUSED_STREAM errors with okhttp. Can you please check?
Tested via https://launchpad.net/~chris-lea/+archive/ubuntu/nginx-devel
It works now!
Thanks -
FYI, okhttp 3.3.0 was released today, see https://github.com/square/okhttp/releases
Hopefully we can re-enable HTTP/2 soon
Raoul -
DAVdroid with okhttp/3.3 has just been released.
So I’m setting this to solved until this problem occurs again with DAVdroid 1.0.9.
-
The new version does not work at all neither with nginx-1.9.13 nor nginx 1.10.0 with both on/off http2. How could I roll back davdroid to the previous version, at least it worked with old nginx?
-
We’ve already released 1.0.9.1 yesterday, it should then work again (because this version uses okhttp 3.3 which is claimed to be compatible with nginx < 1.11.0 HTTP/2 implementations; plus it reverts a change from 1.0.9 which caused
Content-Lengthnot to be sent, which in turn confuses some servers). Please give us a short feedback after you tried it. -
It works fine now. Thanks guys!
-
Tested this morning with 1.0.9.1 and nginx 1.11.0. Works like a charm. Thanks a lot :slight_smile:
