+The Hawks Posted October 13, 2007 Share Posted October 13, 2007 The name geocaching.com resolves to the correct IP, but IIS (?) returns a "Bad Request (Invalid Hostname)" error when using only geocaching.com to access the page. www.geocaching.com workd fine. Is this intentional or did someone mess up IIS's (or whichever web server software is running) virtual host handling? -nik Link to comment
+Yossarian Posted October 13, 2007 Share Posted October 13, 2007 I'm seeing the same thing. (intermittently) It appears that something is misconfigured on the 66.150.167.148 server. When I force my computer to use that IP address (by putting it in the hosts file) for geocaching.com it returns an error. When I force it to use 66.150.167.149 or 66.150.167.150 it gets redirected to www.geocaching.com. I get the same thing when putting those IP addresses in the browser. http://66.150.167.148/ http://66.150.167.149/ http://66.150.167.150/ Link to comment
iryshe Posted October 13, 2007 Share Posted October 13, 2007 Fixed it. Thanks for the heads-up. Link to comment
+The Hawks Posted October 13, 2007 Author Share Posted October 13, 2007 Fixed it. Thanks for the heads-up. Never mind. Sure looks better now Link to comment
+Yossarian Posted October 13, 2007 Share Posted October 13, 2007 Fixed it. Thanks for the heads-up. Yep, workin' again. Thanks Jeremy! Just curious though...why use redirects instead of allowing geocaching.com and www.geocaching.com to be interchangeable? Link to comment
+The Hawks Posted October 13, 2007 Author Share Posted October 13, 2007 Fixed it. Thanks for the heads-up. Yep, workin' again. Thanks Jeremy! Just curious though...why use redirects instead of allowing geocaching.com and www.geocaching.com to be interchangeable? Who said there were any redirects? I think - at least in this thread - we were talking VHosts rather than redirects Link to comment
iryshe Posted October 13, 2007 Share Posted October 13, 2007 Session sharing between geocaching.com and www.geocaching.com are different. Hence the redirects. Link to comment
+Yossarian Posted October 13, 2007 Share Posted October 13, 2007 Who said there were any redirects? I think - at least in this thread - we were talking VHosts rather than redirects I'm the one who said there were redirects. It would appear that redirects (or lack thereof on one of the webservers) is what was causing the problem you were seeing. Link to comment
+The Hawks Posted October 13, 2007 Author Share Posted October 13, 2007 Who said there were any redirects? I think - at least in this thread - we were talking VHosts rather than redirects I'm the one who said there were redirects. It would appear that redirects (or lack thereof on one of the webservers) is what was causing the problem you were seeing. So where did the "Bad Request" originate from? I guessed it was the web server not being able to find a valid VHost for the name given in the Host-heaer. Link to comment
+The Hawks Posted October 13, 2007 Author Share Posted October 13, 2007 (edited) This double posting was created due to the web server killing the PHP script after 45 seconds on my first request Who said there were any redirects? I think - at least in this thread - we were talking VHosts rather than redirects I'm the one who said there were redirects. It would appear that redirects (or lack thereof on one of the webservers) is what was causing the problem you were seeing. So where did the "Bad Request" originate from? I guessed it was the web server not being able to find a valid VHost for the name given in the Host-heaer. Edited October 13, 2007 by The Hawks Link to comment
+Yossarian Posted October 13, 2007 Share Posted October 13, 2007 So where did the "Bad Request" originate from? I guessed it was the web server not being able to find a valid VHost for the name given in the Host-heaer. I believe because their webservers aren't configured to serve anything up at geocaching.com...that's why requests to geocaching.com get redirected to www.geocaching.com. A Virtual Host problem was a good guess but it looks like that doesn't apply in this case. Link to comment
+The Hawks Posted October 13, 2007 Author Share Posted October 13, 2007 So where did the "Bad Request" originate from? I guessed it was the web server not being able to find a valid VHost for the name given in the Host-heaer. I believe because their webservers aren't configured to serve anything up at geocaching.com...that's why requests to geocaching.com get redirected to www.geocaching.com. A Virtual Host problem was a good guess but it looks like that doesn't apply in this case. I don't want to argue that, as it really doesn't matter, but being a system administrator myself I am interested in whether that would trigger an error saying "Invalid hostname"? Link to comment
+Yossarian Posted October 14, 2007 Share Posted October 14, 2007 (edited) I don't want to argue that, as it really doesn't matter, but being a system administrator myself I am interested in whether that would trigger an error saying "Invalid hostname"? Good question. Unfortunately I don't have access to a IIS 6.0 machine or I'd try to replicate that. Now that I think about it...they're probably using Host Headers to handle the redirection...in which case we're both right. Edited October 14, 2007 by Yossarian Link to comment
+The Hawks Posted October 14, 2007 Author Share Posted October 14, 2007 I don't want to argue that, as it really doesn't matter, but being a system administrator myself I am interested in whether that would trigger an error saying "Invalid hostname"? Good question. Unfortunately I don't have access to a IIS 6.0 machine or I'd try to replicate that. Now that I think about it...they're probably using Host Headers to handle the redirection...in which case we're both right. Hmm ... you never know. Anyway, nothing is impossible when using certain software Link to comment
+Yossarian Posted October 19, 2007 Share Posted October 19, 2007 (edited) Broken again You beat me to it! Edited October 19, 2007 by Yossarian Link to comment
Recommended Posts