How to write and propose an RFC?
There’s actually an RFC for that: RFC 7322 – RFC Style Guide.
There’s actually an RFC for that: RFC 7322 – RFC Style Guide.
If you want that format try this: select regexp_replace(rawtohex(sys_guid()) , ‘([A-F0-9]{8})([A-F0-9]{4})([A-F0-9]{4})([A-F0-9]{4})([A-F0-9]{12})’ , ‘\1-\2-\3-\4-\5’) as FORMATTED_GUID from dual Example Results: FORMATTED_GUID ———————————— F680233E-0FDD-00C4-E043-0A4059C654C9
Finally, I received a response from R. Fielding: 202 is a success status. The pointer mentioned is just hypertext in the body of the response. A 303 should be sent if you want to use Location to redirect the client to another resource. The result of the redirected request can be a 202. ….Roy So, … Read more
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
##Short answer The current definition of URL syntax indicates that you never need to percent-encode the asterisk character in the path, query, or fragment components of a URL. HTTP 1.1 As @Riley Major pointed out, the RFC that HTTP 1.1 references for URL syntax has been obsoleted by RFC3986, which isn’t as black and white … Read more
This is your original expression, changed so that it allows several emails separated by semicolon and (optionally) spaces besides the semicolon. It also allows a single email address that doesn’t end in semicolon. This allows blank entries (no email addresses). You can replace the final * by + to require at least one address. (([a-zA-Z0-9_\-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([a-zA-Z0-9\-]+\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})(\]?)(\s*;\s*|\s*$))* … 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