Community
Participate
Working Groups
This may just be a Sharemation thing. I am now able to connect to the site via our provider, which I couldn't before. However, all puts (creating new folder, or putting a file) result in "415 unsupported media type". I am able to generate the sync tree contents and get a file (yeah!) See me for login/password if needed.
It may be that sharemation incorrectly requires a content-type header. RFC2616 sec 7.2.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". The method org.eclipse.webdav.client.AbstractResourceHandle#setContent (InputStream) does not define a content-type, since it cannot be readily determined from the input stream argument. The work-around is to use the DAVClient PUT call directly and set the content header in the context. However, it is probably 'a good thing' to have setContent explicitly set the type to be "application/octet-stream" and a setContent(String type, InputStream content) method on the handle to make this easy. This will be in builds > 20020605
Unable to test against Sharemation because they are sending back malformed responses, that interferes with authentication. Removing this bug report as a F3 milestone item.
[LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX.
