- 10 Mar, 2015 4 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Currently, we use same number of HTTP/2 sessions per worker with given backend addresses. New option to specify the number of HTTP/2 session per worker will follow.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 09 Mar, 2015 5 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
It seems that we don't care about this since we don't change buffer pointer between would-block write/read and next write/read. Somehow we decided we need these fields. As a precaution, we set SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER in SSL_set_mode() for both server and client contexts.
-
Tatsuhiro Tsujikawa authored
It turns out that writing successfully to network is not enough. After apparently successful network write, read fails and then we first know network has been lost (at least my android mobile network). In this change, we say connection check is successful only when successful read. We already send PING in this case, so we just wait PING ACK with short timeout. If timeout has expired, drop connection. Since waiting for PING ACK could degrade performance for fast reliably connected network, we decided to disable connection check by default. Use --backend-http2-connection-check to enable it.
-
Tatsuhiro Tsujikawa authored
-
Kazuho Oku authored
-
- 08 Mar, 2015 12 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Downstream's headers mutation functions have been rewritten to share code.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 07 Mar, 2015 11 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
nghttp2_submit_request and nghttp2_submit_response will set NGHTTP2_FLAG_END_STREAM after all given data is sent (data could be 0). This means we have no way to send trailers. In this commit, we added NGHTTP2_DATA_FLAG_NO_END_STREAM flag. The application can set this flag in *data_flags inside nghttp2_data_source_read_callback. If NGHTTP2_DATA_FLAG_EOF is set, library automatically set NGHTTP2_FLAG_END_STREAM. But if both NGHTTP2_DATA_FLAG_EOF and NGHTTP2_DATA_FLAG_NO_END_STREAM are set, NGHTTP2_FLAG_END_STREAM will not set by library. Then application can use new nghttp2_submit_trailer() to send trailers. nghttp2_submit_trailer() will set NGHTTP2_FLAG_END_STREAM and it is actually thing wrapper of nghttp2_submit_headers().
-
Tatsuhiro Tsujikawa authored
After we sent SETTINGS including ENABLE_PUSH = 0, peer may already issue PUSH_PROMISE before receiving our SETTINGS and react it to SETTINGS ACK. Previously we accept this PUSH_PROMISE. In this commit, we check the pending ENABLE_PUSH value and if it means disabling push, we refuse PUSH_PROMISE with RST_STREAM of error REFUSED_STREAM.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 06 Mar, 2015 8 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-