| Issue 475: | Use HTTP 405 error when POST is used on GET methods | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
It seems like 405 errors would be the best response for when GET is used
for POSTs and when POSTs are used for GETS.
<blockquote>
405 Method Not Allowed
A request was made of a resource using a request method not supported
by that resource; for example, using GET on a form which requires data to
be presented via POST, or using PUT on a read-only resource.
</blockquote>
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_Error
|
||||||||||
,
Apr 20, 2009
This may be something we add in V2 but we chose to use the existing HTTP error code people are handling rather than break existing Twitter developer's code. Marking as milestone V2.
Labels: -Priority-Medium Priority-Low Milestone-V2
|
|||||||||||
,
Apr 20, 2009
Assigning to Matt so this issue has an owner.
Status: Accepted
Owner: m...@twitter.com |
|||||||||||
,
Apr 21, 2009
Moved to http://apiwiki.twitter.com/V2-Roadmap. Marking Invalid so it's out of the way.
Status: Invalid
Labels: -Milestone-V2 |
|||||||||||
,
Apr 30, 2009
I have an iPhone app that makes use of the twitter API to post tweets -- a few weeks ago, a small percentage of my users started getting 405 status codes when my app POST's update.xml for a status update. I am unable to reproduce it locally. Are some twitter gateways running at different API levels? Is update still a POST, or is it a GET now? Are there other reasons my users would see 405's? |
|||||||||||
,
Apr 30, 2009
We do not currently use HTTP 405 for incorrect method, this ticket is suggesting that we do. Update is still a POST and will remain so. I don't know of other reasons for a 405 … there is no code I know of in our system the produces that. |
|||||||||||
 Sign in to add a comment
|
|||||||||||
