Commit 3ee6aa1
fix: return null for infinite lock timeout in DAV properties
When the lock timeout is configured as infinite (-1 minutes), getTimeout()
returns -60 which clients incorrectly interpret as a past expiry timestamp.
Use ETA_INFINITE sentinel check to return null instead, so nc:lock-timeout
is omitted from PROPFIND/LOCK/UNLOCK responses for infinite locks.
Adds regression test verifying that LOCK_TIMEOUT = -1 (the default) produces
ETA_INFINITE rather than a negative timeout value.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: James Manuel <moodyjmz@users.noreply.github.com>1 parent ee018db commit 3ee6aa1
2 files changed
Lines changed: 17 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
142 | | - | |
| 142 | + | |
143 | 143 | | |
144 | 144 | | |
145 | 145 | | |
| |||
278 | 278 | | |
279 | 279 | | |
280 | 280 | | |
281 | | - | |
| 281 | + | |
282 | 282 | | |
283 | 283 | | |
284 | 284 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
387 | 387 | | |
388 | 388 | | |
389 | 389 | | |
| 390 | + | |
| 391 | + | |
| 392 | + | |
| 393 | + | |
| 394 | + | |
| 395 | + | |
| 396 | + | |
| 397 | + | |
| 398 | + | |
| 399 | + | |
| 400 | + | |
| 401 | + | |
| 402 | + | |
| 403 | + | |
| 404 | + | |
390 | 405 | | |
391 | 406 | | |
392 | 407 | | |
| |||
0 commit comments