Change Details

A bug in OkHttp currently prevents us from performing certain actions on an HTTP/2 connection. Details on the upstream bug are here: https://github.com/square/okhttp/issues/2506 https://github.com/square/okhttp/issues/2543 HTTP/2 was enabled on the appservers last week ({T96848}), and as a result, the OkHttp bug resulted in failures to connect when attempting to log in or edit in any version of the app: {T134758} {T134759} We've worked around this for the time being by forcing an HTTP/1.1 connection, but should monitor OkHttp for a fix to the underlying issue so that we can benefit from HTTP/2 when a fix is released.

An implementation issue (arguably, a bug) in how nginx 1.9.x+ negotiates connections currently prevents the Android app from logging in or editing over an HTTP/2 connection. We've worked around this for the time being by forcing an HTTP/1.1 connection, but should monitor nginx for a fix to the underlying issue so that we can benefit from HTTP/2 when a fix is released. Details here: https://trac.nginx.org/nginx/ticket/959 https://lists.w3.org/Archives/Public/ietf-http-wg/2016AprJun/0174.html See also discussion on the OkHttp repo: https://github.com/square/okhttp/issues/2506 https://github.com/square/okhttp/issues/2543 And related bugs triggered by the HTTP/2 rollout: {T134758} {T134759}

A bug in OkHttp currently prevents us from performing certain actions onn implementation issue (arguably, a bug) in how nginx 1.9.x+ negotiates connections currently prevents the Android app from logging in or editing over an HTTP/2 connection. Details on the upstream bug are hereWe've worked around this for the time being by forcing an HTTP/1.1 connection, but should monitor nginx for a fix to the underlying issue so that we can benefit from HTTP/2 when a fix is released. Details here: https://trac.nginx.org/nginx/ticket/959 https://lists.w3.org/Archives/Public/ietf-http-wg/2016AprJun/0174.html See also discussion on the OkHttp repo: https://github.com/square/okhttp/issues/2506 https://github.com/square/okhttp/issues/2543 HTTP/2 was enabled on the appservers last week ({T96848}), and as a result, the OkHttp bug resulted in failures to connect when attempting to log in or edit in any version of the appAnd related bugs triggered by the HTTP/2 rollout: {T134758} {T134759} We've worked around this for the time being by forcing an HTTP/1.1 connection, but should monitor OkHttp for a fix to the underlying issue so that we can benefit from HTTP/2 when a fix is released.