[JCR-1785] If header checking lacks etag checks

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jackrabbit-webdav
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 06/Oct/08 10:49
• Updated: 07/Nov/16 08:02

Description

The evaluation of the WebDAV If header seems to lack Etag checks. For instance, this test case:

public void testPutIfEtag() throws HttpException, IOException, DavException, URISyntaxException {

String testuri = this.root + "iftest";

int status;
try

{ PutMethod put = new PutMethod(testuri); String condition = "<" + testuri + "> ([" + "\"an-etag-this-testcase-invented\"" + "])"; put.setRequestEntity(new StringRequestEntity("1")); put.setRequestHeader("If", condition); status = this.client.executeMethod(put); assertEquals("status: " + status, 412, status); }

finally

{ DeleteMethod delete = new DeleteMethod(testuri); status = this.client.executeMethod(delete); assertTrue("status: " + status, status == 200 || status == 204 || status == 404); }

}

fails, as the PUT request gets executed, although it should have been rejected with Precondition Failed.

Issue Links

• blocks: JCR-4053 RFC4918IfHeaderTest test failures
• relates to: JCR-406 If header evaluation compliance problems