#86 SET_PARAMETER responses

[Magnus Westerlund]

Clarify on the usage of SET_PARAMETER when no body is
present. A correct syntax with unknown headers will
result in a 200 response but also the understanding of
a propreitary or new header will result in 200. Clarify
that a requester should use the Require header with an
option tag to ensure that the responder of the request
really understands the propreitary or new header.

Also write text recommending on the usage of parameters
in the body with the motivation that they are simpler
than using require and headers. But both case should be
possible to use.

How to handle a empty parameter list in the body should
also be explained.

[Rob Lanphier]

Logged In: YES
user_id=3796

From 14 May 2003 telecon
(http://rtsp.org/2003/telecon/minutes14May.html):
# Magnus: how to respond if server doesn't understand parameter
# Anders: maybe a require header to be used if necessary
# Magnus: I can agree with just a clarification
# Anders: for proprietary client request, it can expect
proprietary response
# Magnus: easier if just use body
# Anders: don't need to specify more than that
# Rob: I agree
# Magnus: spec says that SET_PARAMETER can be used for keep
alive
# Magnus: it's possible to have SET_PARAMETER without body
# RESOLUTION: Short explanation of SET_PARAMETER without
body being allowed. No other changes

[Magnus Westerlund]

Logged In: YES
user_id=302620

Added text trying to clarify that it is allowed to use for
keep alive. Also clarified the possible pit-falls with using
headers in such a method.

Please review!

[Magnus Westerlund]

Logged In: YES
user_id=302620

Forgotten to assign it to me.

[Magnus Westerlund]

Logged In: YES
user_id=302620

Solution has been available since march, no comments.
Closing issue.