HTTP/1.1: Method Definitions - The Diigo Meta page

• 20 Mar 15
  

  ken scott

  • The OPTIONS method represents a request for information about the  communication options available on the request/response chain  identified by the Request-URI. This method allows the client to  determine the options and/or requirements associated with a resource,  or the capabilities of a server, without implying a resource action  or initiating a resource retrieval. 

     
  • Responses to this method are not cacheable.

  • If the OPTIONS request includes an entity-body (as indicated by the  presence of Content-Length or Transfer-Encoding), then the media type  MUST be indicated by a Content-Type field. Although this  specification does not define any use for such a body, future  extensions to HTTP might use the OPTIONS body to make more detailed  queries on the server. A server that does not support such an  extension MAY discard the request body. 

     

  • If the Request-URI is not an asterisk, the OPTIONS request applies  only to the options that are available when communicating with that  resource. 

     
  • If no response body is included, the  response MUST include a Content-Length field with a field-value of  "0".

  3 more annotations...

• 08 Feb 15
  

  ppagno
• 10 Jan 15
  

  jeubeda

  rest reference standards soa webservices w3c

• 17 Dec 14
  

  Olivier PEYRUSSE

  html documentation specifications

  • If a resource has been created on the origin server, the response  SHOULD be 201 (Created)
  • 9.6 PUT
  • If a  new resource is created, the origin server MUST inform the user agent  via the 201 (Created) response
  • 200 (OK) or 204 (No Content) response codes
  • existing resource
  • 200 (OK) if the response includes an  entity describing the status
  • or 204 (No Content)

  5 more annotations...

• 15 Sep 14
  

  cosmo89929
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response
  • This method can  be used for obtaining metainformation about the entity implied by the  request without transferring the entity-body itself.
• 19 Jun 14
  

  Golam Kibria
  • If-Modified-Since, If-Unmodified-Since,  If-Match, If-None-Match, or If-Range
  • "conditional GET"
  • Range header field
  • "partial GET"
  • of the resource  identified by the Request-URI in the Request-Line
  • as a new subordinate
  • accept the  entity enclosed
  • as a new subordinate of the resource  identified by the Request-URI in the Request-Line
  • The posted entity  is subordinate to that URI in the same way that a file is subordinate  to a directory containing it
  • Location  header
  • 201 (Created)
  • under the  supplied Request-URI
  • enclosed entity be stored
  • The fundamental difference between the POST and PUT requests is  reflected in the different meaning of the Request-URI
  • The URI in a  POST request identifies the resource that will handle the enclosed  entity.
  • In contrast, the URI in a PUT request identifies the entity enclosed  with the request

  14 more annotations...

• 24 Apr 14
  

  s kwok
  • The GET method means retrieve whatever information (in the form of an  entity) is identified by the Request-URI. If the Request-URI refers  to a data-producing process, it is the produced data which shall be  returned as the entity in the response and not the source text of the  process, unless that text happens to be the output of the process.
  • The POST method is used to request that the origin server accept the  entity enclosed in the request as a new subordinate of the resource  identified by the Request-URI in the Request-Line.
  • The PUT method requests that the enclosed entity be stored under the  supplied Request-URI. If the Request-URI refers to an already  existing resource, the enclosed entity SHOULD be considered as a  modified version of the one residing on the origin server. If the  Request-URI does not point to an existing resource, and that URI is  capable of being defined as a new resource by the requesting user  agent, the origin server can create the resource with that URI.
  • If a  new resource is created, the origin server MUST inform the user agent  via the 201 (Created) response. If an existing resource is modified,  either the 200 (OK) or 204 (No Content) response codes SHOULD be sent  to indicate successful completion of the request. If the resource  could not be created or modified with the Request-URI, an appropriate  error response SHOULD be given that reflects the nature of the  problem. The recipient of the entity MUST NOT ignore any Content-*  (e.g. Content-Range) headers that it does not understand or implement  and MUST return a 501 (Not Implemented) response in such cases.
  • The fundamental difference between the POST and PUT requests is  reflected in the different meaning of the Request-URI.

  3 more annotations...

• 11 Mar 14
  

  Reto Bachmann-Gmür
• 09 Sep 13
  

  Hrvoje -

  http

  • If the OPTIONS request includes an entity-body
  • this  specification does not define any use for such a body
  • If the Request-URI is an asterisk ("*"), the OPTIONS request is  intended to apply to the server in general
  • the "*" request is only useful as a "ping" or "no-op"  type of method
  • A 200 response SHOULD include any header fields that indicate  optional features implemented by the server and applicable to that  resource (e.g., Allow)
  • The response body, if any, SHOULD also include  information about the communication options.
  • If the Request-URI refers to an already  existing resource, the enclosed entity SHOULD be considered as a  modified version
  • the origin server can create the resource with that URI
  • 201 (Created)
  • 200 (OK) or 204 (No Content)
  • The URI in a  POST request identifies the resource that will handle the enclosed  entity.
  • the URI in a PUT request identifies the entity enclosed  with the request
  • 301 (Moved Permanently)
  • A single resource MAY be identified by many different URIs.
  • a PUT request on a general URI might result in  several other URIs being defined

  13 more annotations...

• 28 Aug 13
  

  prakash seetharaman

  http REST spec

• 26 Aug 13
  

  Carlos Cáceres

  Programacion_web

• 22 Sep 12
  

  ucheng
  • GET and  HEAD methods SHOULD NOT have the significance of taking an action  other than retrieval.
• 19 Jun 12
  

  Tudor Milencovici

  HTTP

  • Methods can also have the property of "idempotence" in that (aside  from error or expiration issues) the side-effects of N > 0 identical  requests is the same as for a single request. The methods GET, HEAD,  PUT and DELETE share this property. Also, the methods OPTIONS and  TRACE SHOULD NOT have side effects, and so are inherently idempotent.
  • The fundamental difference between the POST and PUT requests is  reflected in the different meaning of the Request-URI. The URI in a  POST request identifies the resource that will handle the enclosed  entity. That resource might be a data-accepting process, a gateway to  some other protocol, or a separate entity that accepts annotations.  In contrast, the URI in a PUT request identifies the entity enclosed  with the request -- the user agent knows what URI is intended and the  server MUST NOT attempt to apply the request to some other resource.  If the server desires that the request be applied to a different URI,
• 23 Apr 12
  

  karlosmid

  programming

• 07 Mar 12
  

  Mehmet Akyuz

  HTTP/1.1: Method Definitions

  http rest

• 31 Jan 12
  

  Philippe Modard
  • Request-URI
  • described by the conditional header field(s)
  • conditional
  • ange header field
  • cacheable
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response
  • obtaining metainformation
  • server accept the  entity enclosed in the request
  • Annotation
  • message
  • block of data
  • Extending a database through an append operation
  • 204 (No Content)
  • 200  (OK)
  • 201 (Created)
  • 303 (See Other)

  14 more annotations...

• 30 Jan 12
  

  gallypette

  HTTP reference

  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response.
• 19 Dec 11
  

  Louise Rubin

  wolbach

• 07 Oct 11
  

  Esfand S

  http verb top docs

• 23 Sep 11
  

  Matheus Muller

  htpp reference w3c spec protocol

• 05 Sep 11
  

  Fausto Carrera

  web programming development reference ajax

• 06 Jul 11
  

  Giovanni Lofrumento

  Idempotenza

• 26 May 11
  

  Ben Bushoy

  HTTP method definitions

  REST web

• 09 May 11
  

  alphatesla

  side-eff

  http reference method

• 17 Mar 11
  

  left Lu
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response. The metainformation contained  in the HTTP headers in response to a HEAD request SHOULD be identical  to the information sent in response to a GET request.
• 18 Feb 11
  

  sera web

  http

• 06 Feb 11
  

  clopezgarces
  • The GET method means retrieve whatever information (in the form of an  entity) is identified by the Request-URI. If the Request-URI refers  to a data-producing process, it is the produced data which shall be  returned as the entity in the response and not the source text of the  process, unless that text happens to be the output of the process.
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response. The metainformation contained  in the HTTP headers in response to a HEAD request SHOULD be identical  to the information sent in response to a GET request. This method can  be used for obtaining metainformation about the entity implied by the  request without transferring the entity-body itself. This method is  often used for testing hypertext links for validity, accessibility,  and recent modification.

  • The POST method is used to request that the origin server accept the  entity enclosed in the request as a new subordinate of the resource  identified by the Request-URI in the Request-Line. POST is designed  to allow a uniform method to cover the following functions: 

     

          - Annotation of existing resources; 

     

          - Posting a message to a bulletin board, newsgroup, mailing list,         or similar group of articles; 

     

          - Providing a block of data, such as the result of submitting a         form, to a data-handling process; 

     

          - Extending a database through an append operation. 
  • The PUT method requests that the enclosed entity be stored under the  supplied Request-URI. If the Request-URI refers to an already  existing resource, the enclosed entity SHOULD be considered as a  modified version of the one residing on the origin server. If the  Request-URI does not point to an existing resource, and that URI is  capable of being defined as a new resource by the requesting user  agent, the origin server can create the resource with that URI.
  • The DELETE method requests that the origin server delete the resource  identified by the Request-URI.
  • The TRACE method is used to invoke a remote, application-layer loop-  back of the request message. The final recipient of the request  SHOULD reflect the message received back to the client as the  entity-body of a 200 (OK) response.
  • TRACE allows the client to see what is being received at the other  end of the request chain and use that data for testing or diagnostic  information.
  • CONNECT for use with a  proxy that can dynamically switch to being a tunnel

  6 more annotations...

• 24 Jan 11
  

  D C

  If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then the media type MUST be indicated by a Content-Type field. Although this specification does not define any use for such a body, futur

  w3c http reference options

• 20 Jan 11
  

  Carles Barrobés

  http methods reference

• 28 Dec 10
  

  jirijanku

  http rest

• 22 Sep 10
  

  Janet Ward

  Web Html howto

• 21 Sep 10
  

  Tony Pearson

  idempotent

• 30 Aug 10
  

  Tarik Guney
  • The OPTIONS method represents a request for information about the  communication options available on the request/response chain  identified by the Request-URI. This method allows the client to  determine the options and/or requirements associated with a resource,  or the capabilities of a server, without implying a resource action  or initiating a resource retrieval.
  • If the OPTIONS request includes an entity-body (as indicated by the  presence of Content-Length or Transfer-Encoding), then the media type  MUST be indicated by a Content-Type field.
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response. The metainformation contained  in the HTTP headers in response to a HEAD request SHOULD be identical  to the information sent in response to a GET request. This method can  be used for obtaining metainformation about the entity implied by the  request without transferring the entity-body itself. This method is  often used for testing hypertext links for validity, accessibility,  and recent modification.
  • The POST method is used to request that the origin server accept the  entity enclosed in the request as a new subordinate of the resource  identified by the Request-URI in the Request-Line.
  • The PUT method requests that the enclosed entity be stored under the  supplied Request-URI. If the Request-URI refers to an already  existing resource, the enclosed entity SHOULD be considered as a  modified version of the one residing on the origin server.
  • The DELETE method requests that the origin server delete the resource  identified by the Request-URI

  4 more annotations...

• 27 Mar 10
  

  Shane Jennings

  http reference protocol

• 18 Feb 10
  

  icaro79

  Java http

• 27 Sep 09
  

  Kenyth Zeng

  http 1.1 spec

  • it is possible that a sequence of several requests is non-  idempotent, even if all of the methods executed in that sequence are  idempotent.
  • This method allows the client to  determine the options and/or requirements associated with a resource,  or the capabilities of a server, without implying a resource action  or initiating a resource retrieval.
  • If the Request-URI is an asterisk ("*"), the OPTIONS request is  intended to apply to the server in general rather than to a specific  resource.
  • The HEAD method is identical to GET except that the server MUST NOT  return a message-body in the response.
  • The POST method is used to request that the origin server accept the  entity enclosed in the request as a new subordinate of the resource  identified by the Request-URI in the Request-Line.
  • The PUT method requests that the enclosed entity be stored under the  supplied Request-URI.
  • If the Request-URI refers to an already  existing resource, the enclosed entity SHOULD be considered as a  modified version of the one residing on the origin server.
  • The DELETE method requests that the origin server delete the resource  identified by the Request-URI.

  6 more annotations...

• 24 Aug 09
  

  Stefano Pigozzi

  http rfc

• 21 Jul 09
  

  vittoria caranna

  web

• 01 Jul 09
  

  Michael Koert

  http reference protocol PUT

• 18 Jun 09
  

  Lloyd Leung

  The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed to share the same semantics for separately extended clients and servers.
  
  The Host request-header field (section 14.23) MUST a

  reference http w3c rest protocol programming rfc methods method Idempotent

• 11 Jun 09
  

  Thiago Campos

  método http post guet method rfc

• 03 Apr 09
  

  alfred westerveld

  http 1.1 documentation

• 08 Sep 08
  

  jackie yang
  • This method can  be used for obtaining metainformation about the entity implied by the  request without transferring the entity-body itself.
  • This method is  often used for testing hypertext links for validity, accessibility,  and recent modification.
• 22 Mar 08
  

  morningwinter

  Http

• 30 Aug 07
  

  Navneet Kumar

  Browser Web HTTP RFC REST W3C Protocol Specification

  • GET and  HEAD methods SHOULD NOT have the significance of taking an action  other than retrieval.
• 12 Jul 07
  

  anand nirak

  •   The TRACE method is used to invoke a remote, application-layer loop-  back of the request message. The final recipient of the request  SHOULD reflect the message received back to the client as the  entity-body of a 200 (OK) response. The final recipient is either the 

     

      origin server or the first proxy or gateway to receive a Max-Forwards  value of zero (0) in the request (see section 14.31). A TRACE request  MUST NOT include an entity. 

     

      TRACE allows the client to see what is being received at the other  end of the request chain and use that data for testing or diagnostic  information. The value of the Via header field (section 14.45) is of  particular interest, since it acts as a trace of the request chain.  Use of the Max-Forwards header field allows the client to limit the  length of the request chain, which is useful for testing a chain of  proxies forwarding messages in an infinite loop. 

     

      If the request is valid, the response SHOULD contain the entire  request message in the entity-body, with a Content-Type of  "message/http". Responses to this method MUST NOT be cached.
• 14 Jun 07
  

  harry
  • The fundamental difference between the POST and PUT requests is  reflected in the different meaning of the Request-URI. The URI in a  POST request identifies the resource that will handle the enclosed  entity. That resource might be a data-accepting process, a gateway to  some other protocol, or a separate entity that accepts annotations.  In contrast, the URI in a PUT request identifies the entity enclosed  with the request -- the user agent knows what URI is intended and the  server MUST NOT attempt to apply the request to some other resource.  If the server desires that the request be applied to a different URI,
• 21 May 07
  

  adrian kalaveshi

  http reference web w3c

• 21 Jan 07
  

  taylor parsons

  HTTP REST REST_CRUD deli

• 06 Jul 06
  

  quekshuy Quek

  N2NWork imported

• 29 Nov 05
  

  marekw Wawrzynczyk
• 30 May 05
  

  Alan Dean

  The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed to share the same semantics for separately extended clients and servers.

  HTTP w3c

• 03 Apr 05
  

  Navaneethakrishnan Ramakrishnan

  java scwcd certification

• 24 Feb 05
  

  kixxtm

  programming http reference

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.