I have looked at your sample program and did some small modification to
make it behave just like it is specified in the http RFC.
- finish each header line with \r\n and an empty line between header and
body.
- remove spaces from xml (not really needed but is nicer for xml parser)
I have run the program on tomcat 3 with slide deployed as webapp.
Tomcat 4 should make no difference but test your installation with the
slide client.
May I ask why you are not using the client API, is there some
restriction or a feature that is missing, or are you just learning the
protocol ?
Dirk
=============== Outbound Message Headers =================
PROPPATCH /slide/files/a HTTP/1.1
Host: localhost:8080
Connection: TE
TE: trailers, deflate, gzip, compress
Content-Type: text/xml
Content-Length: 142
=============== Outbound Message Body =================
<?xml version="1.0" ?><A:propertyupdate xmlns:A="DAV:"
xmlns:Z="DAV:"><A:set><A:prop><Z:test>dirk</Z:test></A:prop></A:set></A:propertyupdate>
=============== Inbound Stream =================
HTTP/1.0 207 Multi-Status
Set-Cookie2: JSESSIONID=l3oi6f9g61;Version=1;Discard;Path="/slide"
Set-Cookie: JSESSIONID=l3oi6f9g61;Path=/slide
Servlet-Engine: Tomcat Web Server/3.2.2 (JSP 1.1; Servlet 2.2; Java
1.3.0; Windows 98 4.90 x86; java.vendor=Sun Microsystems Inc.)
<?xml version="1.0" encoding="utf-8" ?><d:multistatus
xmlns:d="DAV"><d:response><d:href>/files/a</d:href><d:propstat><d:prop><Z:test
xmlns:Z="DAV:"/></d:prop><d:status>HTTP/1.1 200
OK</d:status></d:propstat></d:response></d:multistatus>
=============== Inbound Stream Complete =================
Vijaya Kumar wrote:
> Thanx Dirk, I got the following response headers from the server. I
> attached the sequence with the source code in the txt file.In short, I
> got HTTP/1.1 200 OK
> Content-Length: 0
> Date: Tue, 28 Aug 2001 09:48:03 GMT
> Server: Apache Tomcat/4.0-b3 (HTTP/1.1
> Connector) but when I again get the Properties using PROPFIND the
> value that I set to that resource is not updated. Whats wrong with
> me?.
Source.java
