Forum Moderators: phranque

Message Too Old, No Replies

HTTP/1.1 400 No Host matches server name

         

jake66

3:51 am on Aug 8, 2006 (gmt 0)

10+ Year Member



HTTP/1.1 400 No Host matches server name www.mysite.com
Date: Tue, 08 Aug 2006 03:46:34 GMT
Server: Apache
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain

- using mod_rewrite.. code:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME}!-f
RewriteCond %{REQUEST_FILENAME}!-d
RewriteRule ^(.*) index.php

problem: when i go to a rewritten link i get a "The page cannot be found" in IE and a blank white page in firefox... when i test the server response i get: HTTP/1.1 400 No Host matches server name

upon hours of searching for a result, i have found a few that sparked my interest.. such as "edit such and such file in your apache config" - which i do not have access to.

however i updated the nameservers approximately 3 hrs ago.
i changed my dns servers (on my pc - to call up a fresh dns cache) to be able to work on the site on the new server (which works fine! UNTIL i try to access a rewritten url)
.. could this be the cause? do i have to wait for the server to update?

fyi: i am on go_d___y hosting, as far as i know they cache just about everything

jdMorgan

2:03 pm on Aug 8, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



In your DNS record, did you declare both "example.com." and "www.example.com".? Or another way to do it is to declare "*.example.com."

If this is already done, then it's possible that (the ServerName for "example.com" on your new hosting is incorrect, OR that the ServerAlias for "www.example.com" is missing) AND (that the server is set with "UseCanonicalName On".)

I suggest you contact the host; If you don't have httpd.conf access, then you won't be able to fix this by yourself. I recommend running with "UseCanonicalName Off" if you want to handle domains and subdomains in .htaccess. But this presumes that httpd.conf is set up to recognize example.com as the ServerName, and at least "www.example.com" as the ServerAlias (with *.example.com as an option if you want to declare and use additional subdomains).

See [httpd.apache.org...] for more details on these directives.

Jim

jake66

4:30 pm on Aug 8, 2006 (gmt 0)

10+ Year Member



i waited overnight and it now works.
however, they're all throwing 404 errors now.

the 404 errors are all in plain html

the url's are supposed to be written as:
mysite.com/CategoryName
mysite.com/ProductName

..there's no extension