HTTP at a glance
Many web developers using HTTP don't think about the protocol itself. This site should provide a basic understanding of HTTP 1.1 and ease the development of web applications that use HTTP.
Given
A
URL,
URI or
IRI,
called resource, with the
scheme
http.
Example
http://example.com
http://www.google.com/?q=http
http://example.org/à-propos/mère
with the following capabilities
-
GET
With the
GETrequest you can retrieve the content of a resource. -
PUT
With the
PUTrequest you can create a new resource or replace the content of a resource. -
POST
With the
POSTrequest you can send data to be processed by the given resource. -
DELETE
With the
DELETErequest you can remove a resource. -
HEAD
With the
HEADrequest you can check the condition of a resource. This request is identical to theGETrequest, but it does not return any content. -
OPTIONS
With the
OPTIONSrequest you can retrieve the capabilities of a resource.
with the following responses
-
200 - Successful
The responses 200 to 299 indicate, that the request was successful.
-
300 - Redirection
The responses 300 to 399 indicate, that the request should be send to another resource.
-
400 - Bad request
The responses 400 to 499 indicate, that the request was malformed.
-
500 - Server error
The responses 500 to 599 indicate, that the request couldn't be answered because of a server error.
Now you know
Now that you know the more or less important glimpses about HTTP 1.1 you could dig a bit further.
- Start developing some true RESTful architectures
- Think about your usage of HTTP requests in your projects you did so far and how you could improve that in the future
- Dig further into the HTTP 1.1 specification and learn more about headers and all the status codes and requests that were not mentioned here
