Who says? The guy who invented REST says: @mnot Oy, yes, PATCH was something I created for the initial HTTP/1.1 proposal because partial PUT is never RESTful. 😉 https://twitter.com/fielding/status/275471320685367296 First of all, REST is an architectural style, and one of its principles is to leverage on the standardized behavior of the protocol underlying it, so … Read more
As quoted from URLPrefix Strings (Windows): When the host element of a UrlPrefix consists of a single plus sign (+), the UrlPrefix matches all possible host names in the context of its scheme, port and relativeURI elements, and falls into the strong wildcard category. When an asterisk (*) appears as the host element, then the … Read more
Section 10.4 of the spec (which you linked to) doesn’t say anything about requirements on responses itself, but instead links to section 7.2.2, which specifies that the server can indicate the length of a response containing an entity body by sending a Content-Length header, or closing the connection when the entire response has been sent. … Read more
If you use a front-end service like Apigee as the front-end to your APIs, you will need something like X-FORWARDED-HOST to understand what hostname was used to connect to the API, because Apigee gets configured with whatever your backend DNS is, nginx and your app stack only see the Host header as your backend DNS … Read more
The RFC for URIs says: 6.2.2.1. Case Normalization When a URI uses components of the generic syntax, the component syntax equivalence rules always apply; namely, that the scheme and host are case-insensitive and therefore should be normalized to lowercase. For example, the URI HTTP://www.EXAMPLE.com/ is equivalent to http://www.example.com/. The other generic syntax components are assumed … Read more
Generally one year is advised as a standard max value. See RFC 2616: To mark a response as “never expires,” an origin server sends an Expires date approximately one year from the time the response is sent. HTTP/1.1 servers SHOULD NOT send Expires dates more than one year in the future. Although that applies to … Read more
There is no HTTP status code 0. What you see is a 0 returned by the API/library that you are using. You will have to check the documentation for that.
Well, note that the request contains binary data, so I’m not posting the request as such – instead, I’ve converted every non-printable-ascii character into a dot (“.”). POST /cgi-bin/qtest HTTP/1.1 Host: aram User-Agent: Mozilla/5.0 Gecko/2009042316 Firefox/3.0.10 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://aram/~martind/banner.htm Content-Type: multipart/form-data; boundary=2a8ae6ad-f4ad-4d9a-a92c-6d217011fe0f Content-Length: 514 … Read more
If you set a cookie like this: Set-Cookie: name=value then the cookie will only apply to the request domain, and will only be sent for requests to the exact same domain, not any other subdomains. (See What is a host only cookie?) Two different domains (e.g. example.com and subdomain.example.com, or sub1.example.com and sub2.example.com) can only … Read more
Part of the problem is that the relevant RFC 2183 doesn’t really state what to do with a disposition type of “inline” and a filename. Also, as far as I can tell, the only UA that actually uses the filename for type=inline is Firefox (see test case). Finally, it’s not obvious that the plugin API … Read more