- 04 Nov, 2013 10 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
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 03 Nov, 2013 3 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 02 Nov, 2013 8 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Using --cacert to load certificate for client certificate authentication is problematic since, --cacert is also used for client mode. This commit adds --verify-client-cacert option which specify the CA certficate file used only for client certificate validation. This change also removes the default certficate load function for client certificate validation.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
It is not clear that SETTINGS_ENABLE_PUSH = 0 disallows HEADERS to the reserved streams. For now, we just check the reception and transmission of PUSH_PROMISE against SETTINGS_ENABLE_PUSH.
-
Tatsuhiro Tsujikawa authored
-
- 01 Nov, 2013 2 commits
-
-
Tatsuhiro Tsujikawa authored
This option requires client certificate and successful verification. Use --cacert option to add CA certificates as necessary.
-
Tatsuhiro Tsujikawa authored
-
- 31 Oct, 2013 3 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
- 30 Oct, 2013 6 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
It is effectively dead code because we should have already submit WINDOW_UPDATE before this case happens.
-
- 29 Oct, 2013 8 commits
-
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
Using this feature, connection level flow control is now enabled in nghttpx.
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
-
Tatsuhiro Tsujikawa authored
The end of request stream is not detected correct place. Also Downstream::end_upload_data() is not called.
-
Tatsuhiro Tsujikawa authored
Now flow control error detection is handled by the library
-
Tatsuhiro Tsujikawa authored
Now we have SETTINGS synchronization, flow control error can be detected strictly. If DATA frame is received with length > 0 and current received window size is equal to or larger than local window size (latter happens when we shirnk window size), it is subject to FLOW_CONTROL_ERROR,
-