HTTP/1.1

https://www.rfc-editor.org/rfc/rfc2616.txt
Admin
Hypertext Transfer Protocol (HTTP/1.1) is an application-level, stateless protocol for distributed,...
Tokens:79,093
Snippets:569
Trust Score:10
Update:1 week ago
Show doc for...
Tokens:
Raw
### HTTP Request Example: GET with Host Header

Source: https://www.rfc-editor.org/rfc/rfc2616.txt

Shows a client request to an origin server using the absolute path form of Request-URI, with the network location in the Host header. The example uses a TCP connection to port 80 of www.w3.org.

```http
GET /pub/WWW/TheProject.html HTTP/1.1
Host: www.w3.org
```

--------------------------------

### GET /pub/WWW/TheProject.html

Source: https://www.rfc-editor.org/rfc/rfc2616.txt

This snippet documents an HTTP GET request that retrieves a resource using the absolute path as described in the HTTP/1.1 specification.

```APIDOC
## GET /pub/WWW/TheProject.html

### Description
Retrieves a resource from the origin server using the absolute path of the URI. The request must include a Host header field with the network location of the URI.

### Method
GET

### Endpoint
/pub/WWW/TheProject.html

### Parameters
#### Path Parameters
- **path** (string) - Required - The absolute path of the resource. If the original URI has no path, it MUST be given as "/".

#### Header Parameters
- **Host** (string) - Required - The network location of the URI (authority), e.g., "www.w3.org".

### Request Example
```
GET /pub/WWW/TheProject.html HTTP/1.1
Host: www.w3.org
```

### Response
#### Success Response (200)
The response contains the resource content. (Specific response details are not provided in the source.)
```

--------------------------------

### GET

Source: https://www.rfc-editor.org/rfc/rfc2616.txt

The GET method retrieves a resource identified by the Request-URI. It is a safe method that should not have side effects. All general-purpose servers MUST support GET.

```APIDOC
## GET /path

### Description
Retrieves the resource identified by the Request-URI.

### Method
GET

### Endpoint
[Request-URI]

### Parameters
#### Request-URI
- **Request-URI** (URI) - Required - The resource identifier (e.g., absolute URI or absolute path). Example: `/pub/WWW/TheProject.html` or `http://www.w3.org/pub/WWW/TheProject.html`.

### Request Example
```
GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1
```

### Response
#### Success Response (200)
- The response contains a representation of the resource.

#### Response Example
(No explicit example provided.)

```

--------------------------------

### GET [Request-URI]

Source: https://www.rfc-editor.org/rfc/rfc2616.txt

The GET method retrieves a resource identified by the Request-URI. It supports conditional requests via If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, or If-Range headersainer, and partial requests via the Range header. Responses may be cacheable per HTTP caching rules.

```APIDOC
GET

### Description
The GET method retrieves the information (entity) identified by the Request-URI. It can be a conditional GET when used with certain headers (If-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match, If-Range) to transfer only under conditions, or a partial GET with a Range header to transfer only part of the entity. The response is cacheable if it meets HTTP caching requirements.
```
Tokens:
Raw