Bug 56163 - HTTP Cache Manager only sends If-None-Match header
Summary: HTTP Cache Manager only sends If-None-Match header
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 2.11
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-19 21:26 UTC by Matt Parker
Modified: 2014-03-17 20:52 UTC (History)
0 users



Attachments
test plan to show that HTTP Cache Manager inserts If-None-Match instead of If-Match for PUT sampler (9.21 KB, text/plain)
2014-02-19 21:26 UTC, Matt Parker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Parker 2014-02-19 21:26:51 UTC
Created attachment 31336 [details]
test plan to show that HTTP Cache Manager inserts If-None-Match instead of If-Match for PUT sampler

When using the HTTP Cache Manager, a PUT sampler should automatically include the "If-Match" header, rather than the "If-None-Match" header, because of the semantics of updates (http://tools.ietf.org/html/rfc2616#section-14.24)
Comment 1 Matt Parker 2014-02-19 21:37:45 UTC
I now see that http://tools.ietf.org/html/rfc2616#section-14.26 says of If-None-Match:

   "It is also used to prevent a method (e.g. PUT)
   from inadvertently modifying an existing resource when the client
   believes that the resource does not exist."

Which actually makes this not a defect, so I am changing to an enhancement ticket--it would probably make sense to put a checkbox on the Cache Manager page for toggling which one it sends for a PUT (along with perhaps other options for processing or ignoring conditional headers).