[Calendar and Contacts Server] #387: Content-type could use its own verifier
#387: Content-type could use its own verifier ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail because the content-type header value doesn't match but is actually valid, e.g. g test for {{{ text/calendar;charset=utf-8 }}} and receive {{{ text/calendar; charset=UTF-8 }}} The space(s) after the semi-colon are valid as is the UC "UTF-8" This might be complicated enough to justify its own verifier -- Ticket URL: <http://trac.calendarserver.org/ticket/387> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#387: Content-type could use its own verifier ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 2: Expected | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | Radar: ----------------------------+----------------------------------------------- Changes (by wsanchez@…): * priority: 5: Not set => 2: Expected -- Ticket URL: <http://trac.calendarserver.org/ticket/387#comment:1> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#387: Content-type could use its own verifier ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 2: Expected | Milestone: Later Component: CalDAV Tester | Severity: Other Keywords: | Radar: ----------------------------+----------------------------------------------- Changes (by wsanchez@…): * milestone: => Later -- Ticket URL: <http://trac.calendarserver.org/ticket/387#comment:2> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
participants (1)
-
Calendar and Contacts Server