No, REST is the way HTTP should be used. Today we only use a tiny bit of the HTTP protocol’s methods – namely GET and POST. The REST way to do it is to use all of the protocol’s methods. For example, REST dictates the usage of DELETE to erase a document (be it a … Read more
GET and POST are two different types of HTTP requests. According to Wikipedia: GET requests a representation of the specified resource. Note that GET should not be used for operations that cause side-effects, such as using it for taking actions in web applications. One reason for this is that GET may be used arbitrarily by … Read more
Although there is the RFC 2965 (Set-Cookie2, had already obsoleted RFC 2109) that should define the cookie nowadays, most browsers don’t fully support that but just comply to the original specification by Netscape. There is a distinction between the Domain attribute value and the effective domain: the former is taken from the Set-Cookie header field … Read more
First off, a “port” is just a number. All a “connection to a port” really represents is a packet which has that number specified in its “destination port” header field. Now, there are two answers to your question, one for stateful protocols and one for stateless protocols. For a stateless protocol (ie UDP), there is … Read more
This has been changed since v32, thanks to @Daniel Alexiuc & @Thanatos for their comments. Current (≥ v32) At the top of the “Network” tab of DevTools, there’s a checkbox to switch on the “Preserve log” functionality. If it is checked, the network log is preserved on page load. The little red dot on the … Read more
Difference between PUT, POST, GET, DELETE and PATCH in HTTP Verbs: The most commonly used HTTP verbs POST, GET, PUT, DELETE are similar to CRUD (Create, Read, Update and Delete) operations in database. We specify these HTTP verbs in the capital case. So, the below is the comparison between them. Create – POST Read – … Read more
Status 422 seems most appropiate based on the spec. The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was … Read more
No. The content-type should be whatever it is known to be, if you know it. application/octet-stream is defined as “arbitrary binary data” in RFC 2046, and there’s a definite overlap here of it being appropriate for entities whose sole intended purpose is to be saved to disk, and from that point on be outside of … Read more
edit 2018-09-13: added some precisions about this pre-flight request and how to avoid it at the end of this reponse. OPTIONS requests are what we call pre-flight requests in Cross-origin resource sharing (CORS). They are necessary when you’re making requests across different origins in specific situations. This pre-flight request is made by some browsers as … Read more
https://httpbin.org/ It echoes the data used in your request for any of these types: https://httpbin.org/anything Returns most of the below. https://httpbin.org/ip Returns Origin IP. https://httpbin.org/user-agent Returns user-agent. https://httpbin.org/headers Returns header dict. https://httpbin.org/get Returns GET data. https://httpbin.org/post Returns POST data. https://httpbin.org/put Returns PUT data. https://httpbin.org/delete Returns DELETE data https://httpbin.org/gzip Returns gzip-encoded data. https://httpbin.org/status/:code Returns given HTTP … Read more