Comments on: HTTP Status 201 causing Flex #2032 Error in IE only

By: Silent Johnny

Silent Johnny — Tue, 12 May 2009 12:55:33 +0000

Ran into the same problem here today. Though it would be easy for me to just change the response to a 200, I think it is not the best solution. You could argue there is no difference between 200 (OK) and 201 (Created), since the latter one only makes sense when creating some entity. However, there is a big difference between a 200 and a 202 (Accepted), if you want to indicate the request is being carried out instead of successful right away.
Furthermore, since there is a lot of interesting development going on in the REST frameworks area, we could use some best practices on the client side.
So, instead of calling the API guys purists, maybe we should try and stick to the standards that are in place and simply check for a HTTP status response. That way, the client side works as supposed, you can take appropriate actions and you can use whatever framework on the server side.

By: Mister

Mister — Wed, 15 Apr 2009 16:40:18 +0000

@Pratyoosh Sharma, You can make a good argument for 404 or 302, but the difference between a 201 and 200 is really the question, what advantage does it have for clients to know that a 201 happened as opposed to a 200? If you look at other API’s (Flickr, Yammer), you won’t find a 201 returned status.

By: Pratyoosh Sharma

Pratyoosh Sharma — Wed, 15 Apr 2009 14:45:30 +0000

I cannot agree with you here, you do care about the HTTP Status being returned from the server as it’s not just the ambiguous “I can’t load the resource” stuff that you are interested in.
E.g. a 404 indicates that resource is unavailable a 302 indicates the alternate source to the resource