Talk:Uniform resource locator
|WikiProject Internet||(Rated C-class, High-importance)|
|WikiProject Computing||(Rated C-class, Mid-importance)|
|Threads older than 1 year may be archived by.|
I'm not a native english speaker, and not registered in the english version of WikiPedia. Bu I would like to tell you that the RFC 1738 is now far obsolete, and that the article should refere to RFC 3986 wich have the status of standard (STD 66).
I may come in few week later to do the update if nobodies have done it... but I prefer native english speaker to do it.
- Yes, it is true, good fella. STD 66 is the way to go. I am right now preparing 110 training hours on lots of topics including this one.
- As of today, this article reads that a URL has "a colon, two slashes" at https://en.wikipedia.org/wiki/Uniform_resource_locator#Syntax. But, according to STD 66, the hierarchical part of a URI may begin with 2 slashes (to be used with path-abempty), 1 slash (in case of path-absolute), and 1 segment (path-rootless). And, let us remember that the hierarchical part may be completely empty (path empty).
- I think the articles for URI, URL and URN must be updated to reflect the current state of the standard.
- Can anyone take care of these changes? I am quite busy now and I usually like to do this kind of things perfect or just not to do them. Gotta get back to work...
- George Rodney Maruri Game (talk) 16:10, 24 November 2013 (UTC)
Representation of URI scheme in article
This article references specific URI schemes (standing alone; not in a URI itself) in a few places using representations such as "http:" and "ftp://", as though the : or // delimiters are part of the scheme name. This isn't a proper way to represent scheme names. These delimiters should only appear in the context of a URI. I'm going to remove the delimiters included in standalone representations of scheme names and display them in a fixed width typeface unless anyone has any objections. 220.127.116.11 (talk) 23:22, 11 March 2014 (UTC)
When I click on any of the
RFC links, I get the following error messages:
- In Firefox 29.0.1:
- Server not found
- Firefox can't find the server at tools.ietf.org.
- In Google Chrome Version 34.0.1847.131 m:
- This webpage is not available
- The server at tools.ietf.org can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
I'm clueless as to how typing
RFC and the section number automatically creates a link that points to tools.ietf.org. I was able to enter the url at web.archive.org to save the page as it appears today, so the page must still be "live". The text of the standard is available at http://www.rfc-editor.org/rfc/rfc3986.txt; perhaps the links should point there instead? Are the existing links working for others? Any ideas as to why I can't access them? Thanks!—D'Ranged 1 talk 23:50, 10 May 2014 (UTC)
- There are some links that the MediaWiki software automatically creates in text when it sees it. For some more information see Help:Magic links.
- The RFC links are live here and go to the correct page at tools.ietf.org. It appears that you are/were having some DNS issues at that time and/or at your location. — Makyen (talk) 01:58, 11 May 2014 (UTC)