-
Notifications
You must be signed in to change notification settings - Fork 836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standard Incompatible with IE8 #621
Comments
+1 |
While I'm sympathetic to browser support, our primary audience isn't browsers, it's other API clients. We can't not use PATCH here, as it's the correct HTTP verb. |
May the standard host a section stating HTTP PUT is ok as long as its a complete resource document? |
+1 |
2 similar comments
+1 |
+1 |
Seems like a popular request. For browsers that don't support PATCH, they should be able to send custom headers, such as I disagree that the primary audience isn't browsers, considering that Ember Data is a major consumer. I agree that it should use PATCH though. |
+1 |
I certainly don't want to talk down the Ember Data case, it is very important! I just mean correctness comes first, then possible hacks for compatibility. |
@ben-crowhurst, |
+1 |
I don't think we need anything normative in the spec to allow for this. This seems like a perfect candidate for an extension, which would allow servers to eventually phase out support. |
I'm +1 on @dgeb's and @steveklabnik's sentiment that we shouldn't spend too much effort worrying about this, as we're doing the correct thing and the problem will solve itself as IE8 fades out over time. That said, a recommendation for how to solve this (if there's a simple way) could be a really big win for the spec adoption at relatively little cost. For example, what if we recommended that clients wanting to do updates over PUT use the |
+1 |
Note that this only recommends _how_ to support PATCHless clients if the server wants to support them at all. It _doesn’t_ go so far as to recommend that they should support them. Closes json-api#621.
Note that this only recommends _how_ to support PATCHless clients if the server wants to support them at all. It _doesn’t_ go so far as to recommend that they should support them. Closes json-api#621.
HTTP PATCH Method not supported :(
http://bugs.jquery.com/ticket/13240
The text was updated successfully, but these errors were encountered: