GET is not appropriate. The user does intend for the error to beMark Baker wrote:
recorded somewhere. That is altering the error log resource on the server.
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.
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?