Bug 22704

Summary: OptionsMethod.java bug - Empty "DAV:" HTTP header values if slide server configured
Product: Slide Reporter: Chris Sharp <csharp>
Component: WebDAV ServerAssignee: Slide Developer List <slide-dev>
Status: RESOLVED FIXED    
Severity: minor    
Priority: P3    
Version: Nightly   
Target Milestone: ---   
Hardware: All   
OS: All   
Attachments: Code fix for duplicate empty "DAV" header in OPTIONS response

Description Chris Sharp 2003-08-25 17:43:13 UTC
Empty "DAV:" HTTP headers when Slide is configured not to use versionControl. Here is a network 
trace:

127.000.000.001.54311-127.000.000.001.08080: OPTIONS /files/ HTTP/1.1
User-Agent: WebDAVFS/1.2.3 (01238000) Darwin/6.6 (Power Macintosh)
Accept: */*
Host: localhost:8080
Content-Length: 0


127.000.000.001.08080-127.000.000.001.54311: HTTP/1.1 200 OK
Content-Length: 0
Allow: PROPPATCH, UNLOCK, COPY, DELETE, TRACE, OPTIONS, POST, HEAD, ACL, GET, REPORT, 
LOCK, PROPFIND, PUT, CONNECT, MOVE
Date: Fri, 22 Aug 2003 23:28:58 GMT
Server: Apache Tomcat/4.0.3 (HTTP/1.1 Connector)
MS-Author-Via: DAV
DAV: 1, 2, slide, access-control
DAV: 
DAV: 
Set-Cookie: JSESSIONID=21F1F5EC1101F5025B93C8E7F7DF21CB;Path=/

The patch included moves the creation of the StringBuffer object in executeRequest() that holds 
the DAV HTTP header value to inside the useVersionControl test. It also moves the resp.addHeader 
call inside useVersionControl as there seems to be no reason to add an empty header - even for a 
Windows client.
Comment 1 Chris Sharp 2003-08-25 17:44:14 UTC
Created attachment 7939 [details]
Code fix for duplicate empty "DAV" header in OPTIONS response