Doing a HTTP PUT from a browser

by

It seems that most browsers don’t support other methods besides GET and POST since it is a limitation of HTML forms.
Here’s another question on the topic:

Are the PUT, DELETE, HEAD, etc methods available in most web browsers?

In order to simulate the PUT, DELETE, etc. methods, you could add a hidden input to a regular GET/POST form with the pseudo-method and have your application translate it so that your controllers see it as if it were a true PUT request, as you mentioned. I’ve seen this method used in google sitebricks (in java – sorry I don’t have any rails-specific reference, but this might at least give you an idea) in this code. I think this is probably the method we are stuck with until something in HTML spec changes (and the browsers with it)

However, GET, POST, PUT and DELETE are supported in AJAX by the major browsers, so there should be no need for a hidden input if you aren’t relying on the HTML form.

More Related Contents:

  1. What is the difference between POST and PUT in HTTP?
  2. Is an entity body allowed for an HTTP DELETE request?
  3. REST HTTP status codes for failed validation or invalid duplicate
  4. URL matrix parameters vs. query parameters
  5. Which status code should I use for failed validations or invalid duplicates?
  6. Detecting the character encoding of an HTTP POST request
  7. Why does my web server software disallow PUT and DELETE requests?
  8. Proper REST response for empty table?
  9. Content-Length header with HEAD requests?
  10. Which HTTP methods match up to which CRUD methods?
  11. HTTP status code for a partial successful request
  12. What is the difference between HTTP and REST?
  13. REST response code for invalid data
  14. Custom HTTP Authorization Header
  15. RESTful Alternatives to DELETE Request Body
  16. Payloads of HTTP Request Methods
  17. REST, HTTP DELETE and parameters
  18. Can I stream a file upload to S3 without a content-length header?
  19. Should I use PATCH or PUT in my REST API?
  20. Is REST DELETE really idempotent?
  21. How can I deal with HTTP GET query string length limitations and still want to be RESTful?
  22. What is the proper HTTP response to send for requests that require SSL/TLS
  23. Do I need Content-Type: application/octet-stream for file download?
  24. What is “406-Not Acceptable Response” in HTTP?
  25. Do I need a content-type header for HTTP GET requests?
  26. Is the URL fragment identifier sent to the server? [duplicate]
  27. Does the HTTP Protocol support multiple content types in response headers?
  28. GET vs. POST Best Practices
  29. Is the Content-Length header required for a HTTP/1.0 response?
  30. What to do with errors when streaming the body of an Http request

Leave a Comment