Anyone have any great ideas besides storing a list of all TLDs? No, because each TLD differs on what counts as a subdomain, second level domain, etc. Keep in mind that there are top level domains, second level domains, and subdomains. Technically speaking, everything except the TLD is a subdomain. In the domain.com.uk example, “domain” … Read more
You can find a nice list of corresponding URL encoded characters on W3Schools. + becomes %2B space becomes %20
If you want to get the value after the hash mark or anchor as shown in a user’s browser: This isn’t possible with “standard” HTTP as this value is never sent to the server (hence it won’t be available in $_SERVER[“REQUEST_URI”] or similar predefined variables). You would need some sort of JavaScript magic on the … Read more
EDIT: As @Jukka K. Korpela correctly points out, RFC 1738 was updated by RFC 3986. This has expanded and clarified the characters valid for host, unfortunately it’s not easily copied and pasted, but I’ll do my best. In first matched order: host = IP-literal / IPv4address / reg-name IP-literal = “[” ( IPv6address / IPvFuture … Read more
From Wikipedia (emphasis and link added): When data that has been entered into HTML forms is submitted, the form field names and values are encoded and sent to the server in an HTTP request message using method GET or POST, or, historically, via email. The encoding used by default is based on a very early … Read more
We had a situation where we needed to persist the URL hash across ASP.Net post backs. As the browser does not send the hash to the server by default, the only way to do it is to use some Javascript: When the form submits, grab the hash (window.location.hash) and store it in a server-side hidden … Read more