[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PaceServiceError GET vs. POST (was Re: AtomPubIssuesList)




Walter Underwood wrote:


GET is not appropriate. The user does intend for the error to be
recorded somewhere. That is altering the error log resource on the server.


Mark Baker wrote:

Whoa, I don't know how I missed that.

"The ErrorURI is used to report violations of the Atom Format
Specification for documents identified with the application/atom+xml
media type."

"report" is an unsafe action. GET is not appropriate. POST would be
my preference, even if there's no body.



We could say "ping". All that's necessary for this to be useful is for the request to be recorded in the access log, along with all the other GETs. No processing is necessary.
No resource is affected, the feed is not removed, etc. Requests to the ErrorURI are also idempotent.


Here is another test for GET: Do you want a web robot to fetch
this with a GET? When it does that, is there a resource it can read?
Would it be useful to save a copy? Cache it?

Is a 204 status code allowed for GET?


Robert Sayre