Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Sender: gc@mnc.ch
To: "HttpClient Project" <httpclient-dev@jakarta.apache.org>
Subject: Re: Getting 200 code when 301 is executed
References: <A68B76BAB1C27346BE22FED8D74ACE2C0283BA@owm-exc-1.telecomsys.com>
	<41DE530C.50207@nose.ch> <87zmzli9tv.fsf@meuh.mnc.ch>
	<41DEA279.8020408@nose.ch>
From: Guillaume Cottenceau <gc@mnc.ch>
Date: 07 Jan 2005 16:00:54 +0100
In-Reply-To: <41DEA279.8020408@nose.ch>
Message-ID: <87r7kxi8rd.fsf@meuh.mnc.ch>
Lines: 19
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Ortwin Gl�ck <ortwin.glueck 'at' nose.ch> writes:

> Guillaume Cottenceau wrote:
> > If I'm correct, this makes HttpClient users unable to be more
> > than "conditionally compliant" with the HTTP specifications. To
> > be fully compliant, one must (e.g. SHOULD is used in RFC) not
> > refer anymore to a permanently moved resource (301), which is not
> > the case with a temporarily moved resource (302), and there is no
> > way to distinguish between these two cases using your proposed
> > technique.
> 
> Yes, I am afraid this is true. Please feel free to add a RFE to the
> issue tracking system.

If you think this can save you some time, I can do that. Just
note that I have never used 3.x myself yet.

-- 
Guillaume Cottenceau

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org