Skip to content

Apply Win32LastModifiedTime on PROPPATCH via set_modified (#68) - #70

Open
BradKollmyer wants to merge 3 commits into
messense:mainfrom
BradKollmyer:win32-last-modified-proppatch
Open

BradKollmyer wants to merge 3 commits into
messense:mainfrom
BradKollmyer:win32-last-modified-proppatch

Conversation

@BradKollmyer

Copy link
Copy Markdown
Contributor

Related to #68.

Windows Explorer sends Win32LastModifiedTime on PROPPATCH. We used to report success without changing mtime. Parse the HTTP-date, call set_modified, and still report 200 so the Windows client keeps working. Malformed values are 409 Conflict.

This branch is stacked on the X-OC-MTime / X-OC-CTime work (it reuses set_modified). The unique commit is the Win32 PROPPATCH change.

messense pushed a commit that referenced this pull request Sep 16, 2026
…68) (#72)

Related to #68.

The crate docs in `src/lib.rs` already describe `X-OC-MTime` /
`X-OC-CTime` and `Win32LastModifiedTime`. The README copies that
"Implemented standards" section but was not updated, so GitHub and
crates.io still omit those extensions.

This adds the same two paragraphs to the README.

Best merged after (or with) #71 and #70, which add the behavior being
documented.
@messense

Copy link
Copy Markdown
Owner

needs a rebase.

Honor ownCloud/Nextcloud timestamp headers on PUT and MKCOL so sync
clients can preserve original modification and creation times.
On platforms that cannot set birth time the cfg leaves that Err as the
final expression, which clippy -D warnings rejects.
Windows Explorer sends that live property; we used to report success
without changing mtime. Parse the HTTP-date, call set_modified, and
still report 200 so the Windows client keeps working. Malformed values
are 409 Conflict.
@BradKollmyer
BradKollmyer force-pushed the win32-last-modified-proppatch branch from d0df238 to 77aba4c Compare September 16, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants