Hi, I'm getting a weird 404 as a response to a PROPFIND. The strange thing is that a PROPFIND from Cadaver works. So I suppose one of the requested properties which triggers the 404? But is the whole result reported 404 then? Something is fishy ;-) Its trunk from today. ---snip--- 192.168.0.125 - - [25/Jul/2008:14:27:45 +0200] "PROPFIND /calendars/ users/user01/ HTTP/1.1" 401 141 "-" "ZideOne/0.8.3 neon/0.27.2" [232.4 ms] 192.168.0.125 - user01 [25/Jul/2008:14:27:45 +0200] "PROPFIND / calendars/users/user01/ HTTP/1.1" 404 113 "-" "ZideOne/0.8.3 neon/ 0.27.2" [116.5 ms] 192.168.0.125 - user01 [25/Jul/2008:14:27:46 +0200] "PROPFIND / calendars/users/user01/ HTTP/1.1" 404 113 "-" "ZideOne/0.8.3 neon/ 0.27.2" [29.3 ms] 192.168.0.111 - - [25/Jul/2008:14:29:27 +0200] "PROPFIND /calendars/ users/user01/ HTTP/1.1" 401 141 "-" "cadaver/0.23.2 neon/0.27.2" [51.7 ms] 192.168.0.111 - user01 [25/Jul/2008:14:29:33 +0200] "PROPFIND / calendars/users/user01/ HTTP/1.1" 207 3062 "-" "cadaver/0.23.2 neon/ 0.27.2" [118.1 ms] ---snap--- Debug log is attached. Thanks, Helge -- Helge Hess http://helgehess.eu/
Hi Helge, --On July 25, 2008 3:21:58 PM +0200 Helge Heß <me@helgehess.eu> wrote:
I'm getting a weird 404 as a response to a PROPFIND. The strange thing is that a PROPFIND from Cadaver works. So I suppose one of the requested properties which triggers the 404? But is the whole result reported 404 then? Something is fishy ;-)
Its trunk from today. ---snip--- 192.168.0.125 - - [25/Jul/2008:14:27:45 +0200] "PROPFIND /calendars/users/user01/ HTTP/1.1" 401 141 "-" "ZideOne/0.8.3 neon/0.27.2" [232.4 ms] 192.168.0.125 - user01 [25/Jul/2008:14:27:45 +0200] "PROPFIND /calendars/users/user01/ HTTP/1.1" 404 113 "-" "ZideOne/0.8.3 neon/0.27.2" [116.5 ms] 192.168.0.125 - user01 [25/Jul/2008:14:27:46 +0200] "PROPFIND /calendars/users/user01/ HTTP/1.1" 404 113 "-" "ZideOne/0.8.3 neon/0.27.2" [29.3 ms] 192.168.0.111 - - [25/Jul/2008:14:29:27 +0200] "PROPFIND /calendars/users/user01/ HTTP/1.1" 401 141 "-" "cadaver/0.23.2 neon/0.27.2" [51.7 ms] 192.168.0.111 - user01 [25/Jul/2008:14:29:33 +0200] "PROPFIND /calendars/users/user01/ HTTP/1.1" 207 3062 "-" "cadaver/0.23.2 neon/0.27.2" [118.1 ms] ---snap---
Debug log is attached.
The error log does not appear to cover the time range where the 404's appear in the access log above. Can you try and find the portion of the error log corresponding to the above times? -- Cyrus Daboo
On 27.07.2008, at 16:08, Cyrus Daboo wrote:
I'm getting a weird 404 as a response to a PROPFIND. The strange thing is that a PROPFIND from Cadaver works. So I suppose one of the requested properties which triggers the 404? But is the whole result reported 404 then? Something is fishy ;-) Debug log is attached.
The error log does not appear to cover the time range where the 404's appear in the access log above. Can you try and find the portion of the error log corresponding to the above times?
The output is from a similiar transaction at a different point in time (the access log isn't any different). Anyways, I have a guess now :-) It appears I (accidently) do a PROPFIND with no content (content-length: 0) which is per RFC the same like a <propfind><all/></propfind>. Maybe this raises the behaviour? I give it a try how it behaves with a detailed GroupDAV PROPFIND. Thanks, Helge -- Helge Hess http://helgehess.eu/
On 27.07.2008, at 21:44, Helge Heß wrote:
Anyways, I have a guess now :-) It appears I (accidently) do a PROPFIND with no content (content-length: 0) which is per RFC the same like a <propfind><all/></propfind>. Maybe this raises the behaviour?
I give it a try how it behaves with a detailed GroupDAV PROPFIND.
Just did, its exactly that. W/o content the PROPFIND raises a 404. W/ content (explicit property selection) it works just fine. Thanks, Helge -- Helge Hess http://helgehess.eu/
participants (2)
-
Cyrus Daboo
-
Helge Heß