Network or I/O error - HTTP 204 had non-zero Content-Length
-
Using DAVx5 with HORDE. Configuration was fine and used to work, but seems now stuck on following error (during sync in background?)
EXCEPTION: java.net.ProtocolException: HTTP 204 had non-zero Content-Length: 20 at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:135) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at at.bitfire.dav4jvm.BasicDigestAuthHandler.intercept(BasicDigestAuthHandler.kt:291) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at at.bitfire.davdroid.HttpClient$UserAgentInterceptor.intercept(HttpClient.kt:244) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:225) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:250) at okhttp3.RealCall.execute(RealCall.java:93) at at.bitfire.dav4jvm.DavResource$put$1.invoke(DavResource.kt:242) at at.bitfire.dav4jvm.DavResource$put$1.invoke(DavResource.kt:34) at at.bitfire.dav4jvm.DavResource.followRedirects(DavResource.kt:378) at at.bitfire.dav4jvm.DavResource.put(DavResource.kt:230) at at.bitfire.davdroid.syncadapter.SyncManager$uploadDirty$1$1.invoke(SyncManager.kt:326) at at.bitfire.davdroid.syncadapter.SyncManager$uploadDirty$1$1.invoke(SyncManager.kt:53) at at.bitfire.davdroid.syncadapter.SyncManager.useRemote(SyncManager.kt:809) at at.bitfire.davdroid.syncadapter.SyncManager$uploadDirty$1.invoke(SyncManager.kt:313) at at.bitfire.davdroid.syncadapter.SyncManager$uploadDirty$1.invoke(SyncManager.kt:53) at at.bitfire.davdroid.syncadapter.SyncManager.useLocal(SyncManager.kt:795) at at.bitfire.davdroid.syncadapter.SyncManager.uploadDirty(SyncManager.kt:304) at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:126) at at.bitfire.davdroid.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:53) at at.bitfire.davdroid.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:835) at at.bitfire.davdroid.syncadapter.SyncManager.performSync(SyncManager.kt:112) at at.bitfire.davdroid.syncadapter.CalendarsSyncAdapterService$CalendarsSyncAdapter.sync(CalendarsSyncAdapterService.kt:55) at at.bitfire.davdroid.syncadapter.SyncAdapterService$SyncAdapter.onPerformSync(SyncAdapterService.kt:73) at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259) SOFTWARE INFORMATION * at.bitfire.davdroid 2.4-ose (279)Generated by SabreDAV 1.8.12-stable
2007-2015 http://sabre.io/
-
HTTP 204 No Content must not have a body and thus Content-Length (which is the definition of 204). It seems like your server has returned HTTP 204 with a body, which does not make sense and can’t be interpreted. Please fix your Web server/application server.