RFC2616 does not dictate what the server must store. Servers are free to store whatever they want. If the client PUTs "Foo" and the server stores "Bar", it's still a valid HTTP PUT request even if it's not what the client expected.
<snip> HTTP/1.1 does not define how a PUT method affects the state of an origin server. </snip> Seems very clear to me. - James Mark Baker wrote: > Probably overdue for a subject change ... > > On 6/14/06, James M Snell <[EMAIL PROTECTED]> wrote: >> You're right about there not being any grey area here. The server >> SHOULD return a 200 or 204 only if the resource has been modified as a >> result of the PUT operation. There is no requirement that the modified >> resource be semantically identical to that included in the PUT request. > > Of course there is, because that's what PUT mean. It doesn't mean "do > whatever you want" (that's POST), nor does it mean "store only the > stuff you understand". It means store. I'm not sure how to explain > it any more simply than that. > > Mark. >
