With all of the discussions about the handling of ETags, If-Match, etc
I thought that I would put up the flowchart we are using to define our
test cases.
With all of the discussions about the handling of ETags, If-Match, etc I thought that I would put up the flowchart we are using to define our test cases. See...
... Thanks for that; a fantastic resource. I've been using it the last few days to implement a simple REST utility for our internal SOA, and this was just what...
... This was put together by me directly from the HTTP spec, it wasn't taken from an FAQ or Wiki but I am not asserting any restrictions on use so if there is...
... Yes. I don't know why, but flickr lowered the resolution of the uploaded file. I will upload a full-res copy over the weekend to my site and publish the...
... I think one thing that is missing is a more generic handling of method names (you may have that somewhere else in your code, but it's missing from the...
... If the file / entity exists and the verb is not in (PUT, POST, DELETE, GET, HEAD) then the flow dictates that a 405 Method Not Allowed is returned. ...
... Understood. I just wanted to clarify that the flow graph is not complete with respect to this (as unsupported methods to an unmapped resource would return...
... Views great in Batik. Pan and zoom without loss of clarity! Thanks Alan. Very useful. regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk...
... If would be great if you could also add a namespace declaration for XLink. This will make it work in Firefox :-) xmlns:xlink="http://www.w3.org/1999/xlink"...
... I still dispute the allowing POST to non-existent resources. If it doesn't exist, how can you POST into it. 404 or 410 IMO. Which incidentally is another...
... 404 just means no representations are available (source), and doesn't necessarily mean that there isn't any processing logic there (sink). Most HTML form...
... If it's there and I can POST to it but not GET it then a GET should return 405 Method Not Allowed with POST in the Allow header. Then I know that it's...
... I've had a think about this and read the spec again. So far as I can tell, the spec does not forbid POSTing onto a missing resource. So I have remodelled...
... I think that text should read more like: "Known that it will never exist again" and point to "410 Gone, or 404". If it might come back, 404 is still the...
... OK, fair point. It does however raise the question: "What should happen if a PUT is made to a resource where it is known that it will never exist again?" ...
... It's expected that it will not exist again, not guaranteed. Certainly if it's deemed very likely that something will be PUT there again it should be a 404 ...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
Offline 
Send Email
