|
RFC 2068 - Hypertext Transfer Protocol -- HTTP/1.1. R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee. (15893 words) |
 | RFC 2068 HTTP/1.1 January 1997 SHOULD This word or the adjective "recommended" means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. |
| RFC 2068 HTTP/1.1 January 1997 The syntax and registry of HTTP language tags is the same as that defined by RFC 1766 [1]. |
| RFC 2068 HTTP/1.1 January 1997 9.5 POST The POST method is used to request that the destination server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. |
| RFC 2068 (15922 words) |
| Standards Track [Page 7] RFC 2068 HTTP/1.1 January 1997 SHOULD This word or the adjective "recommended" means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. |
| Standards Track [Page 11] RFC 2068 HTTP/1.1 January 1997 Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin server. |
| Standards Track [Page 50] RFC 2068 HTTP/1.1 January 1997 9.5 POST The POST method is used to request that the destination server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. |
Feeds |
Contact