Just for the information of the list....
I don't think there is anything we can do about this, other that tell the user to fix their browser configuration as Brian has done. It would be nice if Apache could just deliver the english version when no acceptable variant is found.
Fixing the server to fallback to .en seems like a good idea; another possibility would be to fall back to no language (index.html instead of index.html.??) if no match is found. This would let the user choose a fallback other than .en without adding a directive for this obscure case.
Chris Pepper
---------- Forwarded message ---------- Date: Mon, 11 Dec 2000 02:12:21 -0800 (PST) From: Brian Behlendorf <[EMAIL PROTECTED]> To: RecUsr1 <[EMAIL PROTECTED]> Cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Ap. Server Doc inaccessible
That would be the expected answer you'd get if you don't have language en as an acceptable language. Check your browser configs - are you emitting an "Accept-Language" header, and if so, what does it say?
Brian
On Mon, 11 Dec 2000, RecUsr1 wrote:http://httpd.apache.org/docs/
"Not Acceptable An appropriate representation of the requested resource /docs/ could not be found on this server. Available variants: * index.html.en <index.html.en> , type text/html, language en * index.html.ja.jis <index.html.ja.jis> , type text/html, language ja, charset iso-2022-jp
Apache/1.3.15-dev Server at httpd.apache.org Port 80"
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Chris Pepper | Shooting Gallery Interactive | 212 905-2200 Mac OS X Software: <http://www.mosxsw.com/> Mac OS X article: <http://db.tidbits.com/getbits.acgi?tbart=06227>
