Forum Moderators: DixonJones
209.214.170.** - - [07/Dec/2003:19:23:07 -0800] "GET /index.html[b]?[/b] HTTP/1.1" 200 20402 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" While it is true, I do have and index.html in no way do I have a "?" at the end.
Assuming they typed it in, any ideas what they want to do, or what they're trying to see?
Thanks.
Pendanticist.
If I add a "?" trailing my .html it renders a 200 as well. (Didn't know that the other day.) Whereas I'd have thought the request would render a 404 since the requested file simply does not exist.
Many of my URLs utilize both case and if a request is made of the server for an all lower-case file (where that file is mixed case), it will be served a 404.
(e.g.)
This_File_Extension
vs.
this_file_extension
Any url other than those actually published to the Internet should not be accessible, correct?
Just one of the miriad of oddities, I suppose. Who knows...
Thanks.
Pendanticist.
How? Why?
Because adding a? to the end of the URL doesn't actually change the page content (in the case of dynamic URLs), but makes the URL look different to the proxy server, this technique sucessfully retrieves a fresh copy.
JP
In the case shown, the query string is empty. Since it is not considered to be part of the URL-path, the server responds with a 200-OK.
Many dynamic sites use this type of setup, for example, putting a session ID there to track the user through the site and associate that user with a particular "shopping cart." However, search engine spiders don't do a good job of spidering URLs with many query-string parameters, which is why there is always a booming business here in questions about how to use static-looking URLs on a dynamic site.
Since there was no referrer -- meaning it could very well be a type-in URL -- jpjones' explanation seems likely for this case.
Jim
If I add a "?" trailing my .html it renders a 200 as well. (Didn't know that the other day.) Whereas I'd have thought the request would render a 404 since the requested file simply does not exist.
The file does exist -- "?" indicates the end of the file name and the beginning of a CGI query string. (As per the spec [hoohoo.ncsa.uiuc.edu]: "QUERY_STRING is defined as anything which follows the first? in the URL.") Whether or not the file is actually capable of parsing the query string is a separate issue.
Any url other than those actually published to the Internet should not be accessible, correct?
Incorrect; that wouldn't allow for support of server scripts with free-form input.