- From: <D.White@mcs.surrey.ac.uk>
- Date: Wed, 03 Sep 1997 15:11:05 +0100
- To: www-talk@w3.org
- cc: D.White@mcs.surrey.ac.uk
Hello everyone, Quick question: For a while, I've used quite a lot of link URLs of the form: http:/a/b/c/d.html I meant this as a document on the same server as the current document, hence no //server part, but I (rather unusually) specified that the protocol was http: to stop Web browsers trying to look it up as file: as well.. Needless to say, this worked fine on all the Web browsers I've ever tried, and no-one has ever reported any of my links of utterly broken! Now, through a whole series of events involving a new search engine, we consulted the RFCs, and they appear to imply that http: MUST be followed by a //server part. This is certainly the interpretation that the search engine uses, and thus it fails to index documents beyond such links! What do people think? Is that what the RFCs or any other standards actually say? Or mean:-)? Is it reasonable? I've gone through removing loads of http: prefixes from URLs w/o a server part... I'll be happy to summarise any replies.. cheers, duncan ------------------------------------------------------------------------------ Duncan C. White, Senior Computing Officer, Dept of Maths and Computing Science, University of Surrey, Guildford, Surrey GU2 5XH, UK. Email: D.White@mcs.surrey.ac.uk Phone: +441 483 259632 URL: http://www.mcs.surrey.ac.uk/showstaff?D.White Fax: +441 483 259385 PGPkey: http://www.mcs.surrey.ac.uk/Personal/D.White/pgpkey.html Key fingerprint = 91 93 0D 90 D0 5E 62 BF 57 39 08 56 43 FC E5 C8 ------------------------------------------------------------------------------ "After all, this is a species whose principal means of population control are famine, abortion, a high infant death rate and war." Intervention (page 442) - Julian May ------------------------------------------------------------------------------
Received on Wednesday, 3 September 1997 10:11:16 UTC