Connected: An Internet Encyclopedia
9.1.1 Safe Methods

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2068
Up: 9 Method Definitions
Up: 9.1 Safe and Idempotent Methods
Prev: 9.1 Safe and Idempotent Methods
Next: 9.1.2 Idempotent Methods

9.1.1 Safe Methods

9.1.1 Safe Methods

Implementers should be aware that the software represents the user in their interactions over the Internet, and should be careful to allow the user to be aware of any actions they may take which may have an unexpected significance to themselves or others.

In particular, the convention has been established that the GET and HEAD methods should never have the significance of taking an action other than retrieval. These methods should be considered "safe." This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is made aware of the fact that a possibly unsafe action is being requested.

Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request; in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the side-effects, so therefore cannot be held accountable for them.


Next: 9.1.2 Idempotent Methods

Connected: An Internet Encyclopedia
9.1.1 Safe Methods