walkero
/
nghttp2
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Be a bit more liberal about what methods accept message bodies.

This commit is contained in:
Jim Morrison 2012-02-15 13:49:02 -08:00
parent d04449eb28
commit f05a67641f
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
lib/includes/spdylay/spdylay.h
View File

@ -411,11 +411,12 @@ void* spdylay_session_get_stream_user_data(spdylay_session *session,
* also lower-cases all names in |nv|.
*
* If |data_prd| is not NULL, it provides data which will be sent in
* subsequent DATA frames. In this case, "POST" must be specified with
* "method" key in |nv|. If |data_prd| is NULL, SYN_STREAM have
* FLAG_FIN. |stream_user_data| can be an arbitrary pointer, which
* can be retrieved by spdylay_session_get_stream_user_data(). Since
* stream ID is not known before sending SYN_STREAM frame and the
* subsequent DATA frames. In this case, a method that allows request
* message bodies (http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9)
* must be specified with "method" key in |nv| (e.g. POST). If |data_prd| is
* NULL, SYN_STREAM have * FLAG_FIN. |stream_user_data| can be an arbitrary
* pointer, which can be retrieved by spdylay_session_get_stream_user_data().
* Since stream ID is not known before sending SYN_STREAM frame and the
* application code has to compare url, and possibly other header
* field values, to identify stream ID for the request in
* spdylay_on_ctrl_send_callback(). With |stream_user_data|, the