If your goal is to verify if your application can open a URL, here is what you can do. Although safari can open the URL, the website might not exist or it might be down. // Swift 5 func verifyUrl (urlString: String?) -> Bool { if let urlString = urlString { if let url = … 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
Originally it was used as an anchor to jump to an element with the same name/id. However, nowadays it’s usually used with AJAX-based pages since changing the hash can be detected using JavaScript and allows you to use the back/forward button without actually triggering a full page reload.
I recently wrote a URL encoder, so this is pretty fresh in my mind. http://site/gwturl#user:45/comments All the characters in the fragment part (user:45/comments) are perfectly legal for RFC 3986 URIs. The relevant parts of the ABNF: fragment = *( pchar / “/” / “?” ) pchar = unreserved / pct-encoded / sub-delims / “:” / … Read more
Well there are two methods to access this data easier, but the interface doesn’t offer the possibility to get the whole URL with one call. You have to build it manually: public static String makeUrl(HttpServletRequest request) { return request.getRequestURL().toString() + “?” + request.getQueryString(); } I don’t know about a way to do this with any … Read more
The query component is indicated by the first ? in a URI. “Query string” might be a synonym (this term is not used in the URI standard). Some examples for HTTP URIs with query components: http://example.com/foo?bar http://example.com/foo/foo/foo?bar/bar/bar http://example.com/?bar http://example.com/?@bar._=???/1: http://example.com/?bar1=a&bar2=b (list of allowed characters in the query component) The “format” of the query component is … Read more
In the simplest case, just do X <- read.csv(url(“http://some.where.net/data/foo.csv”)) plus which ever options read.csv() may need. Edit in Sep 2020 or 9 years later: For a few years now R also supports directly passing the URL to read.csv: X <- read.csv(“http://some.where.net/data/foo.csv”) End of 2020 edit. Original post continutes. Long answer: Yes this can be done … Read more
Form data (for GET or POST) is usually encoded as application/x-www-form-urlencoded: this specifies + for spaces. URLs are encoded as RFC 1738 which specifies %20. In theory I think you should have %20 before the ? and + after: example.com/foo%20bar?foo+bar
The term ‘slug’ comes from the world of newspaper production. It’s an informal name given to a story during the production process. As the story winds its path from the beat reporter (assuming these even exist any more?) through to editor through to the “printing presses”, this is the name it is referenced by, e.g., … Read more
HTTP RFC 2396 defines path separator to be single slash. However, unless you’re using some kind of URL rewriting (in which case the rewriting rules may be affected by the number of slashes), the uri maps to a path on disk, but in (most?) modern operating systems (Linux/Unix, Windows), multiple path separators in a row … Read more