No subject

should issue the OPTIONS method, as illustrated in RFC 2326, Section 10
(DESCRIBE is for describing the media); however, I believe that OPTIONS
only describes the available methods, not the available header entities
(eg - CSeq, Session, Transport, etc). It sounds like the best way to
figure out if header entities are supported is by sending them and seeing
if the server responds with an Unsupported header entity (RFC 2326,
Section 13.41).

Unfortunately both the OPTIONS method and the Unsupported header entity
are not required for RFC compliant implementations (RFC 2326, Appendix
D.1) and it seems like nobody has even attempted to write an RFC compliant
RTSP server so far...

Perhaps the other trick is to use the Server header entity (RFC 2326,
Section 13.36) which is recommended to be implemented in even minimal
implementations.

-- 
This is the streaming mailing-list, see http://www.videolan.org/streaming/
To unsubscribe, please read http://www.videolan.org/support/lists.html