Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <040f01c15dc1$4553ddc0$93c0b0d0@roweclan.net>
From: "William A. Rowe, Jr." <wrowe@covalent.net>
To: <dev@httpd.apache.org>
References: <ELEDJONBOPPAEGANDEEIMEEGCAAA.joshua@slive.ca>
 <060401c15cf1$8f632e00$93c0b0d0@roweclan.net> <3BD82820.AB69B36F@Golux.Com>
Subject: Re: results with 2.0.27-dev on daedalus :-)
Date: Thu, 25 Oct 2001 20:53:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "Rodent of Unusual Size" <Ken.Coar@Golux.Com>
Sent: Thursday, October 25, 2001 9:56 AM


> "William A. Rowe, Jr." wrote:
> > 
> > To be RFC compliant we must start by fixing today's wrong behavior.
> > 
> > User accepts .en and .fr at q=.5, server chooses one
> > [WRONG: MULTIPLE_CHOICES should be presented!!!]
> 
> Both of those are at q=0.5, or only .fr?

At eqivilant quality.  Were they different, the higher value would win.

> > User accepts no specified, we serve none [Also wrong,
> > also MULTIPLE_CHOICES should be the default behavior!!!]
> 
> Unclear.  What about a request for foo.html, with no
> Accept-Language field but with 'Accept: text.html',
> and files foo.html.en, foo.html.fr, and foo.html.html?
> Are you suggesting we should send a 300 for that instead
> of foo.html.html?

Forget foo.html.html, we hope to do away with that this time around.

Presuming no other factors, two languages available, and _no_ stated
accept, we should present MULTIPLE_CHOICES as in the case above.

All this is overridden at the administrator's discression.  I'm just
pointing out where we went wrong; it confused the issue when coding this
patch to start from the wrong point.

Bill