WebDAV PROPFIND returns Go zero time (Mon, 01 Jan 0001) as getlastmodified for collections #665

New issue

Closed

opened 2026-09-23 02:47:19 +00:00 by Cordy · 0 comments

Cordy commented

2026-09-23 02:47:19 +00:00

Owner

Found in the #656 QA pass (v0.6.247, files.c0rdyceps.ch).

Matrix row: §7 "WebDAV mount" (protocol correctness; not covered by interop-rclone's assertions).

Steps

PROPFIND /dav/home/_qa/sub/   Depth: 1

Seen: the collection's own response carries

<getlastmodified>Mon, 01 Jan 0001 00:00:00 GMT</getlastmodified>

while the child file in the same multistatus has a real timestamp (Wed, 23 Sep 2026 02:45:34 GMT). The web UI shows sub/ as modified 02:45, so the UI computes a time from somewhere but WebDAV emits the Go time.Time{} zero value.

Expected: either a real timestamp (latest child mtime, or folder-marker time) or omit the property. RFC 4918 allows an absent getlastmodified on collections.

Why it matters: Finder, Cyberduck and rclone display or sort by this and will show folders as modified in year 1. Some clients also treat an implausible date as a parse failure.

Found in the #656 QA pass (v0.6.247, files.c0rdyceps.ch). **Matrix row:** §7 "WebDAV mount" (protocol correctness; not covered by interop-rclone's assertions). **Steps** ``` PROPFIND /dav/home/_qa/sub/ Depth: 1 ``` **Seen:** the collection's own response carries ``` <getlastmodified>Mon, 01 Jan 0001 00:00:00 GMT</getlastmodified> ``` while the child file in the same multistatus has a real timestamp (`Wed, 23 Sep 2026 02:45:34 GMT`). The web UI shows `sub/` as modified 02:45, so the UI computes a time from somewhere but WebDAV emits the Go `time.Time{}` zero value. **Expected:** either a real timestamp (latest child mtime, or folder-marker time) or omit the property. RFC 4918 allows an absent `getlastmodified` on collections. **Why it matters:** Finder, Cyberduck and rclone display or sort by this and will show folders as modified in year 1. Some clients also treat an implausible date as a parse failure.