7 Commits

Author	SHA1	Message	Date
Daniel Mack	8062cfdf42	Add support for charset information in content-type header ... Altough not explicitly allowed by RFC2326, some servers respond with a `Content-Type` header field that contains charset information as described in RFC2616 (sec 14.17). The parser currently fails to read from such connections and bails with `unsupported Content-Type header '[application/sdp; charset=utf-8]'` Change this by ignoring everything after a semicolon.	2021-06-25 19:05:40 +02:00
aler9	dde57ee568	remove ID and BaseURL from Track	2021-06-23 23:07:55 +02:00
aler9	d073a185c2	client: allow to publish tracks with pre-existing control attribute (#48)	2021-06-23 22:03:22 +02:00
aler9	d07e93f245	auth: simplify	2021-05-30 12:52:46 +02:00
aler9	70c0dc7800	remove base.MustParseURL	2021-05-23 16:48:56 +02:00
aler9	f2f9b644c6	simplify tests	2021-05-07 23:51:23 +02:00
aler9	712432bcef	client: move test files	2021-05-04 16:51:20 +02:00