We are delivering our php3 content using the ForceType directive with (apparently) no problems to normal browsers. However we have discovered that search engine crawlers don't like the content and return an Error 406 Not Suitable message. Something to do with content negotiation?
Example URL: http://www.laterooms.com/en/country1.html
When submitted to Altavista at : http://add-url.altavista.com/cgi-bin/newurl?
we get
You have entered the following URL: http://www.laterooms.com/en/country1.html We tried to fetch this page but received an Error 406. The usual causes of an Error 406 are a mistyped URL or the page could not be retrieved from the Web site you entered. This page will be removed from the AltaVista index.
Any ideas??
Regards, Paul Walsh
below is the result of "lynx -head http://www.laterooms.com/en/country1.html" ############################# HTTP/1.1 302 Found Date: Wed, 25 Apr 2001 17:26:40 GMT Server: Apache/1.3.12 (Unix) PHP/3.0.16 mod_ssl/2.6.2 OpenSSL/0.9.5a X-Powered-By: PHP/3.0.16 Location: http://www.uk.laterooms.com/index.php3?lang=eng Connection: close Content-Type: text/html X-Pad: avoid browser bug #############################
"302" is the error that the resource has been relocated temporarily. the remote browser should then look at the location: header and be redirected to "http://www.uk.laterooms.com/index.php3?lang=eng"
its likely that the altavista script doesn't like the "302" error and the redirection. have you tried to submit to altavista the URL "http://www.uk.laterooms.com/index.php3?lang=eng"?
I also have this problem. On a normal browser my pages load fine, but when spidered by altavista or google, or viewed on some really old browsers, the server returns a 406 error.
I am also using a setup similar to paul walsh\'s.
Has anybody figured out this problem yet?
This same problem occurs with Lynx. Has something to do with content-negotitation, but I'm not sure how to change the apache config to make sure this does not happen.
Hi!
I think the problem is when you have MultiViews turned on in Apache and you're not giving an complete URL ... Apache tries to send the right file ... and for .php-Files the MIME type is configured as "application/x-httpd-php". That's not compatible with "text/*" Google and other spiders are sending.
What I forgot to wrote: The bugfix for this is to use a .var-File that tells apache the right mime-type. See http://httpd.apache.org/docs/content-negotiation.html for a description.
