It's a plone based site, plone based servers do not run on port 80 by default, and how I run my is use mod_rewrite to rewrite the requests and have plone servee through apache.magick1 wrote:I appear it is the way IE handles the cookie the site sends (I18N_LANGUAGE=en).
That, and the server behaves strangely (doesn't work with the good old telnet to port 80 :confused. But every browser I have tried (even Lynx
Haven't tried Trinis suggestion yet (I am in Linux at the moment and to lasy to launch Wine).
So people don't have to go to domain.com
ort they just go to domain.com (implied port 80).It should return a response of some kind if you telnet to port 80 then do GET /:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidd
en</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access
/
on this server.</p>
<hr>
<address>Apache/2.0.54 (Debian GNU/Linux) mod_ssl/2.0.54
OpenSSL/0.9.7e Server at web.nevrax.com Port 80</address>
</body></html>
They're running the same sort of apache/mod_rewrite setup I am/was (server is dead atm).
But, if they are missing en-gb, en-ca, etc, then someone has setup the internationalization settings too narrowly, they need to provide the same content for all the 'variants' as they do for 'en' or 'en-us' -- en-us is the default for Microsoft Windows, everything works set to en-us, guaranteed. It's probable that whoever tested used that setting, and didn't try the 'other' English languages lol.
I've made that mistake myself
.
