jmarya/knowledge
jmarya/knowledge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

restructure

Browse source
This commit is contained in:
JMARyA 2024-01-17 09:00:45 +01:00
parent ef7661245b
commit 598a10bc28
Signed by: jmarya
GPG key ID: 901B2ADDF27C2263
182 changed files with 342 additions and 336 deletions
Download patch file Download diff file Expand all files Collapse all files

16
technology/internet/HTTP.md
View file

@ -331,7 +331,7 @@ Headers can be grouped according to their contexts:
### Informational responses
- `100 Continue`: This interim response indicates that the client should continue the request or ignore the response if the request is already finished.
- `101 Switching Protocols`: This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.
- `102 Processing` ([WebDAV](../tools/WebDAV.md)): This code indicates that the server has received and is processing the request, but no response is available yet.
- `102 Processing` ([WebDAV](WebDAV.md)): This code indicates that the server has received and is processing the request, but no response is available yet.
### Successful responses
- `200 OK`: The request succeeded.
@ -340,8 +340,8 @@ Headers can be grouped according to their contexts:
- `204 No Content`: There is no content to send for this request, but the headers may be useful. The user agent may update its cached headers for this resource with the new ones.
- `205 Reset Content`: Tells the user agent to reset the document which sent this request.
- `206 Partial Content`: This response code is used when the `Range` header is sent from the client to request only part of a resource.
- `207 Multi-Status` ([WebDAV](../tools/WebDAV.md)): Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
- `208 Already Reported` ([WebDAV](../tools/WebDAV.md)): Used inside a `<dav:propstat>` response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
- `207 Multi-Status` ([WebDAV](WebDAV.md)): Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
- `208 Already Reported` ([WebDAV](WebDAV.md)): Used inside a `<dav:propstat>` response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
### Redirection messages
- `300 Multiple Choices`: The request has more than one possible response. The user agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but [HTML](HTML.md) links to the possibilities are recommended so the user can pick.)
@ -371,9 +371,9 @@ Headers can be grouped according to their contexts:
- `417 Expectation Failed`: This response code means the expectation indicated by the Expect request header field cannot be met by the server.
- `418 I'm a teapot`: The server refuses the attempt to brew coffee with a teapot.
- `421 Misdirected Request`: The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
- `422 Unprocessable Content` ([WebDAV](../tools/WebDAV.md)): The request was well-formed but was unable to be followed due to semantic errors.
- `423 Locked` ([WebDAV](../tools/WebDAV.md)): The resource that is being accessed is locked.
- `424 Failed Dependency` ([WebDAV](../tools/WebDAV.md)): The request failed due to failure of a previous request.
- `422 Unprocessable Content` ([WebDAV](WebDAV.md)): The request was well-formed but was unable to be followed due to semantic errors.
- `423 Locked` ([WebDAV](WebDAV.md)): The resource that is being accessed is locked.
- `424 Failed Dependency` ([WebDAV](WebDAV.md)): The request failed due to failure of a previous request.
- `425 Too Early Experimental`: Indicates that the server is unwilling to risk processing a request that might be replayed.
- `426 Upgrade Required`: The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).
- `428 Precondition Required`: The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
@ -389,7 +389,7 @@ Headers can be grouped according to their contexts:
- `504 Gateway Timeout`: This error response is given when the server is acting as a gateway and cannot get a response in time.
- `505 HTTP Version Not Supported`: The HTTP version used in the request is not supported by the server.
- `506 Variant Also Negotiates`: The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
- `507 Insufficient Storage` ([WebDAV](../tools/WebDAV.md)): The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
- `508 Loop Detected` ([WebDAV](../tools/WebDAV.md)): The server detected an infinite loop while processing the request.
- `507 Insufficient Storage` ([WebDAV](WebDAV.md)): The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
- `508 Loop Detected` ([WebDAV](WebDAV.md)): The server detected an infinite loop while processing the request.
- `510 Not Extended`: Further extensions to the request are required for the server to fulfill it.
- `511 Network Authentication Required`: Indicates that the client needs to authenticate to gain network access.