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