You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue a LOCK request like this one:
LOCK /dav/testdata/copied/exists1.txt HTTP/1.1
X-Daydream-Test: LOCK a resource with two Timetype values
Host: calendars
Depth: 0
Timeout: Infinite, Second-4100000000
Authorization: Basic amFja2M6YmVydGhh
Content-Length: 205
What is the expected output?
The LOCK request should succeed (or fail for some other reason), because the Timeout header is not invalid.
What do you see instead?
HTTP/1.1 400 Bad request
Date: Tue, 19 Oct 2010 14:55:01 GMT
Server: Apache/2.2.14 (Debian)
X-Powered-By: PHP/5.3.2-2
Content-Length: 270
Connection: close
Content-Type: application/xml; charset=utf-8
What client software are you using?
Custom Java test-rig
Please provide any additional information below.
See http://tools.ietf.org/html/rfc4918#section-9.10.9 (example):
"In this request, the client has
specified that it desires an infinite-length lock, if available,
otherwise a timeout of 4.1 billion seconds, if available."
Original author: ipqu...@gmail.com (October 19, 2010 15:10:29)
What steps will reproduce the problem?
LOCK /dav/testdata/copied/exists1.txt HTTP/1.1
X-Daydream-Test: LOCK a resource with two Timetype values
Host: calendars
Depth: 0
Timeout: Infinite, Second-4100000000
Authorization: Basic amFja2M6YmVydGhh
Content-Length: 205
<D:lockinfo xmlns:D='DAV:'>
<D:lockscope><D:exclusive/></D:lockscope>
<D:locktype><D:write/></D:locktype>
<D:owner>
<D:href>http://dav/principals/jackc</D:href>
</D:owner>
</D:lockinfo>
2.
3.
What is the expected output?
The LOCK request should succeed (or fail for some other reason), because the Timeout header is not invalid.
What do you see instead?
HTTP/1.1 400 Bad request
Date: Tue, 19 Oct 2010 14:55:01 GMT
Server: Apache/2.2.14 (Debian)
X-Powered-By: PHP/5.3.2-2
Content-Length: 270
Connection: close
Content-Type: application/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre_DAV_Exception_BadRequest</s:exception>
<s:message>Invalid HTTP timeout header</s:message>
<s:sabredav-version>1.3.0</s:sabredav-version>
</d:error>
What version of the product are you using?
1.3.0
What client software are you using?
Custom Java test-rig
Please provide any additional information below.
See http://tools.ietf.org/html/rfc4918#section-9.10.9 (example):
"In this request, the client has
specified that it desires an infinite-length lock, if available,
otherwise a timeout of 4.1 billion seconds, if available."
See http://tools.ietf.org/html/rfc4918#section-10.7:
"TimeOut = "Timeout" ":" 1#TimeType" (i.e. one or more of TimeType)
Original issue: http://code.google.com/p/sabredav/issues/detail?id=98
The text was updated successfully, but these errors were encountered: