Community
Participate
Working Groups
I have spent a number of hours attempting to get the WebDAV plugin to connect to a Jakarta-Slide based (WebDAV Construction Kit) WebDAV server. It will make the initial authentication and provide a listing of collections in the WebDAV Import dialog, but click "Next >" eventually leads to a "Problem Occurred - Read timed out". As far as I can tell, a possible fix was proposed back in April of 2004: http://dev.eclipse.org/mhonarc/lists/platform-webdav-dev/msg00065.html I cannot tell if this was ever applied since it looks like the sources in CVS have moved.
Sorry for the delay. There isn't any current work being done on the WebDAV plug-in. I just released the change to org.eclipse.webdav to HEAD.
I built the plug-in from the HEAD, but ended up with the same result. Looks like the above change did not address the time-out issue. If I get a chance, I will look into it more now that I have the source.
The "Read timed out" appears to have been due to extensive logging on the server, but that was only masking an "Unexpected end of stream" problem. Doing some debugging with the webdav client source, I have determined that the http client does not handle the response to an HTTP HEAD command generated by Tomcat 5.0.28. Below are the request and the response: Request: 0000 00 20 ed 6c 5b ce 00 06 1b c3 3e 9f 08 00 45 00 . .l[.....>...E. 0010 00 95 4f b1 40 00 80 06 28 28 c0 a8 00 6a c0 a8 ..O.@...((...j.. 0020 00 cf 04 7c 25 80 9c e7 fa 65 7c 74 fb cb 50 18 ...|%....e|t..P. 0030 44 70 87 75 00 00 48 45 41 44 20 2f 77 65 62 64 Dp.u..HEAD /webd 0040 61 76 2f 64 74 64 73 20 48 54 54 50 2f 31 2e 31 av/dtds HTTP/1.1 0050 0d 0a 48 6f 73 74 3a 20 77 61 6c 6d 61 72 74 31 ..Host: walmart1 0060 3a 39 36 30 30 0d 0a 41 75 74 68 6f 72 69 7a 61 :9600..Authoriza 0070 74 69 6f 6e 3a 20 42 61 73 69 63 20 59 57 52 74 tion: Basic YWRt 0080 61 57 34 36 59 57 52 74 61 57 34 3d 0d 0a 43 6f aW46YWRtaW4=..Co 0090 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 30 0d ntent-Length: 0. 00a0 0a 0d 0a ... Response: 0000 00 06 1b c3 3e 9f 00 20 ed 6c 5b ce 08 00 45 00 ....>.. .l[...E. 0010 01 58 6c 07 40 00 80 06 0b 0f c0 a8 00 cf c0 a8 .Xl.@........... 0020 00 6a 25 80 04 7c 7c 74 fb cb 9c e7 fa d2 50 18 .j%..||t......P. 0030 fd 93 41 91 00 00 48 54 54 50 2f 31 2e 31 20 32 ..A...HTTP/1.1 2 0040 30 30 20 4f 4b 0d 0a 50 72 61 67 6d 61 3a 20 4e 00 OK..Pragma: N 0050 6f 2d 63 61 63 68 65 0d 0a 43 61 63 68 65 2d 43 o-cache..Cache-C 0060 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 61 63 68 65 ontrol: no-cache 0070 0d 0a 45 78 70 69 72 65 73 3a 20 57 65 64 2c 20 ..Expires: Wed, 0080 33 31 20 44 65 63 20 31 39 36 39 20 31 36 3a 30 31 Dec 1969 16:0 0090 30 3a 30 30 20 50 53 54 0d 0a 53 65 74 2d 43 6f 0:00 PST..Set-Co 00a0 6f 6b 69 65 3a 20 4a 53 45 53 53 49 4f 4e 49 44 okie: JSESSIONID 00b0 3d 39 34 30 45 33 31 30 45 32 32 30 42 34 42 36 =940E310E220B4B6 00c0 32 31 30 31 38 34 39 38 36 32 31 41 35 31 38 38 21018498621A5188 00d0 38 3b 20 50 61 74 68 3d 2f 77 65 62 64 61 76 0d 8; Path=/webdav. 00e0 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 74 .Content-Type: t 00f0 65 78 74 2f 68 74 6d 6c 3b 63 68 61 72 73 65 74 ext/html;charset 0100 3d 55 54 46 2d 38 0d 0a 54 72 61 6e 73 66 65 72 =UTF-8..Transfer 0110 2d 45 6e 63 6f 64 69 6e 67 3a 20 63 68 75 6e 6b -Encoding: chunk 0120 65 64 0d 0a 44 61 74 65 3a 20 4d 6f 6e 2c 20 31 ed..Date: Mon, 1 0130 38 20 41 70 72 20 32 30 30 35 20 31 37 3a 30 39 8 Apr 2005 17:09 0140 3a 30 36 20 47 4d 54 0d 0a 53 65 72 76 65 72 3a :06 GMT..Server: 0150 20 41 70 61 63 68 65 2d 43 6f 79 6f 74 65 2f 31 Apache-Coyote/1 0160 2e 31 0d 0a 0d 0a .1.... The problem appears to be that an HttpConnection$ChunkedInputStream is being used to read in the stream and it requires there to be a body after the headers. It specifically dies trying to read text representing the size of the chunked stream after the headers. As you can see, this is not in the stream. According to RFC 2616 sec 9.4: "The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response." I've tried getting around this by making it more tolerant, but have yet to be successful. I'm just not familiar enough with the code or HTTP yet. Any ideas?
3.1M7 is a historical milestone, does not make sense to have an open defect in this state. Tom, the WebDav plugin is not being actively worked on anymore.
(In reply to comment #3) > I've tried getting around this by making it more tolerant, but have yet to be > successful. I'm just not familiar enough with the code or HTTP yet. Any > ideas? Have a look at DAVExplorer http://www.ics.uci.edu/~webdav/ If it works, adopt the code from that (it's released under s BSD style license).
This component is no longer being actively developed. We encourage users to investigate the capabilities of the Eclipse Web Tools Project.
