right, the grammar looks to accept an empty body Allow hdr....but I
haven't found any mentions about the meaning of an empty body...just:
20.5 Allow
The Allow header field lists the set of methods supported by the UA
generating the message.
All methods, including ACK and CANCEL, understood by the UA MUST be
included in the list of methods in the Allow header field, when
present. The absence of an Allow header field MUST NOT be
interpreted to mean that the UA sending the message supports no
methods. Rather, it implies that the UA is not providing any
information on what methods it supports.
Supplying an Allow header field in responses to methods other than
OPTIONS reduces the number of messages needed.
have you found some thing else? ...even so, IMHO the purpose of a
contact which forbids all methods looks strange to me...
anyhow, this case didn't work even with the former implementation -
parse_methods function returns error if an empty string is supplied
(empty as content, not length)....
regards,
bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
> on double thinking, the only confusion may appear between (1) not parsed
> yet and (2) parsed but no method found - header with no
> payload... right?
no. an empty allow header
Allow:
is perfectly legal meaning that the UA doesn't accept any methods.
Allow = "Allow" HCOLON [Method *(COMMA Method)]
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
