J
Jan said:
Could be anything. Might not even be a file. Why would it matter to a
visitor anyway?
Yes, anything. Could be anything. But what is it?
Isn't it a file like that one:
janfaerber.com/archiv/spam/mortage_www.savedatcash.com/x/d37/index.lsd
I just want to save this file and I would like to use the same name as on
their server.
Or store
it on a filesystem (or in a database) which can say "blah/" is an HTML
document.
I think with IE I could get this name by selecting 'save as...'. But with
opera, mozilla & co. they don't get file names which fit with the real
name.
Or let me put the question in another way:
Why must the visitor not know the name of such a file?
For security reason?
Jan said:http://www.savedatcash.irrelevant> Here is the directory view where they have d37/ - it is not a html
document. Or do you think it could be one but they use a gif for a
directory because the name looks like one?
I think with IE I could get this name by selecting 'save as...'. But with
opera, mozilla & co. they don't get file names which fit with the real
name.
Or let me put the question in another way:
Why must the visitor not know the name of such a file?
For security reason?
The filename isn't a secret, it is mearly so irrelevant so as to be not
worth mentioning.
... So why do I get here '404 Not Found' instead of '405 Method Not
Allowed'? When I paste www.savedatcash.com into the browser I get a
smilie.
In reality, you can never know for sure what the actual file name is on
the server. It has nothing to do with the browser (MSIE vs Firefox, for
example) and everything to do with how the web server is configured.
... So why do I get here '404 Not Found' instead of '405 Method Not
Allowed'? When I paste www.savedatcash.com into the browser I get a smilie.
Jan Faerber said:JDS ... output:
So is THIS the difference between URI (= Uniform Ressource Identifier) and
URL (= Uniform Ressource Locator)? A link to a directory in contrast to a
link to a file in a directory?
Agreed.
I don't know the technical difference between URI and URL. But that is not
what I was talking about. A webserver can be configured to obfuscate the
names of files and directories in ways which you cannot predict without
talkign to the webserver admin. *That's* waht I'm talking about.
JDS said:I don't know the technical difference between URI and URL. But that is not
what I was talking about. A webserver can be configured to obfuscate the
names of files and directories in ways which you cannot predict without
talkign to the webserver admin.
You mean *security by obscurity*.
Absolutely nothing to do with security.
Jan Faerber said:
If that's the only resource you've been using no wonder you're
confused about the difference between URL and URI.
The two cases discussed up thread:
http://www.example.com/foo/
and
http://www.example.com/foo/bar.html
are both URLs and hence are both URIs (as URIs are a superset of
URLs).
Steve
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.