Comment 3 for bug 79785

I think that SchoolTool is wrong in requiring the Content-Type header.

I looked in RFC 2445 (iCalendar), but didn't find it specifically mentioned
that this header is mandatory.

Excerpt from RFC 2616 (HTTP/1.1)

   Any HTTP/1.1 message containing an entity-body SHOULD include a
   Content-Type header field defining the media type of that body. If
   and only if the media type is not given by a Content-Type field, the
   recipient MAY attempt to guess the media type via inspection of its
   content and/or the name extension(s) of the URI used to identify the
   resource. If the media type remains unknown, the recipient SHOULD
   treat it as type "application/octet-stream".

However, I did submit a wishlist bug
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266382)

Here are the headers provided by KOrganizer:

PUT /persons/manager/calendar.ics HTTP/1.1
Connection: Keep-Alive
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)
Pragma: no-cache
Cache-control: no-cache
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*
Accept-Encoding: x-gzip, x-deflate, gzip, deflate
Accept-Charset: utf-8, utf-8;q=0.5, *;q=0.5
Accept-Language: en
Host: localhost:7080
Cookie: auth=50a7d99dc116b084c6aeb3f4d213521c9ec2fdd1
Content-Length: 969

BEGIN:VCALENDAR
...