Keep in mind that all of the previous answers refer to the commonly-accepted spec for REST and its relatives. But a web server can respond however it wants to any call it wants; HTTP calls are received in plain text and the server can choose to interpret and use (or completely ignore) the verb. None of this is inherent to HTTP calls, it's just a norm that most APIs choose to follow.
This is a really good point to make. When I was learning about REST the first time, I was told what the different verbs do. I was a little confused and trying to figure out how it was enforced programmatically, only to find out that it wasn't. You could technically create things with GET, it's just bad/unconventional API design.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Keep in mind that all of the previous answers refer to the commonly-accepted spec for REST and its relatives. But a web server can respond however it wants to any call it wants; HTTP calls are received in plain text and the server can choose to interpret and use (or completely ignore) the verb. None of this is inherent to HTTP calls, it's just a norm that most APIs choose to follow.
This is a really good point to make. When I was learning about REST the first time, I was told what the different verbs do. I was a little confused and trying to figure out how it was enforced programmatically, only to find out that it wasn't. You could technically create things with GET, it's just bad/unconventional API design.