HTTP 1.1 protocol includes 9 methods : GET, POST, PUT, DELETE and others.

At the same time HTML 5.1 assumes the use of only two of them in the forms : GET and POST:

The following are the keywords and states:

  • The keyword get , mapping to the state GET , indicating the HTTP GET method.
  • The keyword post , the mapping to the state POST , indicating the HTTP POST method.

Why are the others not supported or used? What is the basis of this architectural solution?

In particular, if the logic of my application implies an idempotent deletion of an element, how and why should I choose between, by definition, non-idempotent POST and GET not appropriate in the sense?

Inspired by the discussion of the XSRF vulnerability response .

  • four
    One small amendment - html implies GET and POST for forms . And it sounds like the rest of the methods cannot be used with HTML - Darth
  • one
    I very much doubt that someone other than the authors of the draft will be able to answer the question "What is the basis of such an architectural solution?". - VenZell
  • one
    And by what criteria should someone vote for the closure? This is not a duplicate; the question is clearly described and guaranteed to be reproduced; written in Russian; does not imply discussion (i.e. it does not contain a message of the form, but what do you think ..? ). - ߊߚߤߘ
  • one
    @Arhad, in theory, "The question gives rise to endless debates and discussions based not on knowledge, but on opinions." And why so, I already answered - only the draft authors and no one else can answer the question. The rest can speculate. - VenZell
  • one
    @VenZell draft draft authors can explain their decisions, information about the specification may be available outside it. w3c does just that: a draft is being written, a discussion is underway (and it can be generally everywhere), the implementation is being sawn, the draft is being rewritten ... therefore there will not necessarily be someone's opinion, someone may know the official position of the draft draft author. - Sasha Omelchenko

1 answer 1

That is the question .

In short, once it was even proposed to support these methods in forms, so that browsers without the support of the scripting engine could fulfill such requests, other points of view were in favor, a full discussion of the link. And Mozilla even added their support in the beta version of their browser, but it did not go further.

Well, here, though stingy, the answer to your question from those who accepted the standard. Then the status was changed to "WONTFIX". Actually, it's all about semantics.

PUT a form payload. It doesn’t payload.