Forum Moderators: phranque
Something is not right, because an attempt to request "www.example.com" from your server isn't actually possible -- the request would be malformed on arrival. A normal browser request for this URL would look like this:
GET / HTTP/1.1
Host: www.example.com
GET HTTP/1.1(no slash, one or two spaces after "GET")
Host: www.example.com
Look for some other mod_rewrite or mod_alias code that may be removing the slash.
Jim
"GET /" is not a response code, it is a client request header.
It may be that IE6 fixes-up the slashless-URL request before sending it to your server (as it should) but does not show the fixed-up URL in its address bar, whereas Firefox fixes up the slashless request before transmission and does display the fixed-up URL in its address bar. IE7 appears to show the fixed-up request URL as well.
If you want to see the HTTP requests and responses to/from your server, try the "Live HTTP Headers" extension for Mozilla browsers. It's a great tool.
Jim
Okay so looks like no problem..
I am a bit conserned about G&A&M
Had a few exploit attacks on my domains already..
I am makings sure there is no posibility of canonical duplication for all cases...
I even give 404s to improbable query strings...
We don't want the nasty proxies on our backs.
<__>
Thanx for your help.
Igor
www dot seoconsultants dot com/tools/headers/
What is good about this tool it also displays the the 200 OK page
in a browser simulator.
Which is important for SE. If you are using a 301 redirect and get 200 OK but the page is not displayed in the browser simulator, it will give you an error.
So if the page is not displayed in browser simulator then GYM will not index it properly and will not be able to follow the anchor links.