The recipient of the entity must NOT ignore any Content-* (e.g.
SSL tunneling 44 ).
However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.For example, this can be used to test a proxy for http/1.1 compliance (or lack thereof).Send a GET request.Safe and Idempotent Methods.1.1, safe Methods, implementors should be aware that the software represents the user in their interactions over the Internet, and should be careful to allow the user to be aware of any actions they might take which may have an unexpected.This allows user agents to represent other methods, such as post, PUT and delete, in a special way, so that the user is made aware of the fact that a possibly unsafe action is being requested.See section.1.3 for security considerations when used for forms.
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.
Responses to this method must NOT be cached.
If a resource has been created on the origin server, the response should be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location header (see section.30 ).
If the server desires that the request be applied to a different URI, it must send a 301 (Moved Permanently) response; the user agent MAY then make its own decision regarding whether or not to redirect the request.
NtentType "text/json should definitely be: ntentType "application/json Other than that I don't see anything wrong with your current code.
The semantics of the GET method change to a "partial GET" if the request message includes a Range header field.
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.If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries should be treated as stale.form method"put" is invalid html and will be treated like form,.e.This method is often used for testing hypertext links for validity, accessibility, and recent modification.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.A server that does not support such an extension MAY discard the request body.HttpClient ) which is specifically tailored for those needs.A trace request must NOT include an entity.You might also want to checkout the.The response to a GET request is cacheable if and only if it meets the requirements for http caching described in section.The set of common methods for http/1.1 is defined below.Http/1.1 does not define how a PUT method affects the state of an origin server.Options, the options method represents a request for information about the communication options available on the request/response chain identified by the Request-URI.