That is more misinformation.
Browsers can access content either locally or over a network.
When accessing content locally, they may be able to use the local filesystem naming conventions.
Thus people using Windows accessing content in a browser locally can use “C:\path\file name”
However when accessing content over a network using HTTP, etc, they must use the URL format.
The URL format says that / is the directory separator and that whitespace must be escaped.
Thus everyone must use “http://hostname/path/file%20name”
In fact Internet Explorer realizes that trying to access “http://hostname\filename” is not proper and automatically corrects it for you. This is what happens:
- User types in link to “http://hostname\index.html”
- Internet Explorer changes Address bar to “http://hostname\index.html”
- Internet Explorer sends proper HTTP request headers:
GET /index.html HTTP/1.1
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705)
Cache-Control: no-cachePeople who do not know that software designed for Microsoft Windows platform can generate HTML with local filesystem paths that are incompatible with the Web experience problems with images not showing up.
Perl / MySQL / HTML CSS