The term comes from the days of ARPANET, the predecessor to the internet, where the researchers would basically just throw ideas out there to, well, make a request for comments from the other researchers on the project. They could be about pretty much anything and were not very formal at the time. If you go … Read more
I don’t see where RFC1738 disallows periods (.) in URLs. Here are some excerpts from there: hpath = hsegment *[ “https://stackoverflow.com/” hsegment ] hsegment = *[ uchar | “;” | “:” | “@” | “&” | “=” ] uchar = unreserved | escape unreserved = alpha | digit | safe | extra safe = “$” … Read more
With your way of counting, the domain name a.b.c.d.e. would be considered to be five characters long. It suspect that not many people will find that way of counting useful. That way of counting also makes the maximum length vary with the number of labels, so when you have four labels the maximum length is … Read more
It has to do with how the browser packages binary and form data for transmission over HTTP. By default only form data is sent, but if the form needs to support uploading a file, then the binary data must also be appended and separated from the form data. Scott Hanselman gives a good explanation of … Read more
As you can see here, Last-Modified header has datetimes in RFC2616 format. In section 14.29 Last-Modified you can see that date format should be: “Last-Modified” “:” HTTP-date An example of its use is Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT Another quote from RFC2616 read more : All HTTP date/time stamps MUST be represented in … Read more
They are not forbidden, it’s CGI legacy. See “Missing (disappearing) HTTP Headers“. If you do not explicitly set underscores_in_headers on;, nginx will silently drop HTTP headers with underscores (which are perfectly valid according to the HTTP standard). This is done in order to prevent ambiguities when mapping headers to CGI variables, as both dashes and … Read more
You are probably looking for RFC 6056 – Recommendations for Transport-Protocol Port Randomization (“Best Current Practice”). Technically there is no requirement that the ephemeral port be >1024 or random (you could build a system that always initiates connections from port 12 because you like the number 12), it’s just not “normal” to do so (and … Read more
The reason this question still often arises is because, as you mentioned, somewhere somehow someone presumed as important wrote that the RFC states domain names without subdomain in front of them are not valid. If you read the RFC carefully, however, you’ll find that this is not exactly what it says. In fact, RFC 1912 … Read more
From the RFC 4648: Base encoding of data is used in many situations to store or transfer data in environments that, perhaps for legacy reasons, are restricted to US-ASCII data. So it depends on the purpose of usage of the encoded data if the data should be considered as dangerous. But if you’re just looking … Read more
It is generally considered a good practice to serve localhost, 0.0.127.in-addr.arpa and the RFC-1918 reverse zones on your internal DNS system to prevent sending queries from them out to the internet. It saves time (you get replies for those queries quickly), bandwidth (no requests leaving your network for zones that shouldn’t exist), and relieves the … Read more