It’s actually not really clearly stated in the standard (RFC 3986) whether a percent-encoded version of . or .. is supposed to have the same this-folder/up-a-folder meaning as the unescaped version. Section 3.3 only talks about “The path segments . and ..”, without clarifying whether they match . and .. before or after pct-encoding. Personally … Read more
Unfortunately the standard DNS A-record (domain name to IP address) used by web-browsers to locate web-servers does not include a port number. Web-browsers use the URL protocol prefix (http://) to determine the port number (http = 80, https = 443, ftp = 21, etc.) unless the port number is specifically typed in the URL (for … Read more
File extensions are not used because of the idea that URIs (and therefore URLs) should be independent of implementation – if you want to access the CDC’s information about food safety, you should be able to go to https://www.cdc.gov/foodsafety (for example). Whether the CDC’s servers are using PHP or Python or Perl doesn’t matter to … Read more
Probably the easiest way is going to be to modify your users table to add 2 extra columns, OR if you don’t want to modify the existing table you could add a new dependent table called “UserPasswordReset” or something like that. The columns are like this: PasswordResetToken UNIQUEIDENTIFIER, PasswordResetExpiration DATETIME If you go with the … Read more
Update: I did some more research and found that using new URL is easily fast enough, and IMO the most straight-forward way of doing this. It is important to note that every method I’ve tried takes less than 1ms to run even on an old phone. So performance shouldn’t be your primary consideration unless you … Read more
History lesson. There was a time when the Web did not dominate the Internet. An organisation with a domain (e.g. my university, aston.ac.uk) would typically have several hostnames set up for various services: gopher.aston.ac.uk (Gopher is a precursor to the World-wide Web), news.aston.ac.uk (for NNTP Usenet), ftp.aston.ac.uk (FTP – including anonymous FTP archives). They were … Read more
I’ve noted 2 approaches to RESTful URI design: hierarchical & filtered I feel hierarchical is overly verbose, has the potential for redundant endpoints (not DRY) and disguises in what resource’s state you’re really interested (after all, REST = representational state transfer). I favor Simple URIs Simple is elegant. I’d choose a URI structure like GET … Read more
RFC 3986 defines Uniform Resource Identifiers. A relative reference that begins with a single slash character is termed an absolute-path reference. A relative reference that does not begin with a slash character is termed a relative-path reference. href=”foo/bar.html” is a relative reference, specifically a relative-path reference. href=”/foo/bar.html” is a relative reference with an absolute path … Read more
I have just tried this. What you attempted to do is correct. In HTML if you are writing a link the & characters should be encoded as & You would only encode the & as %26 if you wanted a parameter value to contain an ampersand. I just wrote a simple HTML page that contained … Read more
Localization is part of Content-Negotiation in Restful API. So my preferred way I would do it through headers. HTTP offers standard way of defining wanted language. Have a look at Accept-Language header.