[
https://issues.apache.org/jira/browse/JCR-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-2739.
--------------------------------
Assignee: Jukka Zitting
Fix Version/s: 2.2.0
Resolution: Fixed
Good point! I increased the timeout to ten seconds in revision 998057.
> RFC4918IfHeaderTest.testPutIfLockToken could fail with 412 Precondition Failed
> ------------------------------------------------------------------------------
>
> Key: JCR-2739
> URL: https://issues.apache.org/jira/browse/JCR-2739
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-webdav
> Affects Versions: 2.2.0
> Reporter: Javier Godoy
> Assignee: Jukka Zitting
> Priority: Trivial
> Fix For: 2.2.0
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> In org.apache.jackrabbit.webdav.server.RFC4918IfHeaderTest:110 (webdav-test),
> the lock request is initialized with a timeout of 1800 milliseconds, which is
> rounded as Timeout: Second-1 (at
> org.apache.jackrabbit.webdav.header.TimeoutHeader:46).
> The assertion in the finally block MUST fail (412, Precondition Failed) if
> the lock has expired (cf. RFC 4918, Section 10.4.10).
> The lock request should be initialized with a higher timeout, at least
> several seconds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
