- From: John W. James <jjames@firstfloor.com>
- Date: Thu, 11 Apr 96 13:59:18 PDT
- To: www-talk@w3.org
I should have been clearer and said that I'm only sending over the HEAD, not a GET HEAD. --- Begin Included Message --- To: "John W. James" <jjames@firstfloor.COM> Cc: www-talk@w3.org Subject: Re: GET HEAD to Proxy In-Reply-To: <9604111714.0D0584@james-hill-farm.firstfloor.COM.firstfloor.COM> Message-Id: <Pine.SGI.3.91.960411130251.1017B-100000@shellx.best.com> X-Url: http://www.wnetc.com/ Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-From: www-talk@w3.org X-Mailing-List: <www-talk@w3.org> archive/latest/2547 X-Loop: www-talk@w3.org Sender: www-talk-request@w3.org Resent-Sender: www-talk-request@w3.org Precedence: list Content-Length: 979 Status: Actually, you just want to use HEAD as in HEAD / HTTP/1.0 I suspect the server was confused by seeing two methods (GET and HEAD) in the same request. On Thu, 11 Apr 1996, John W. James wrote: > Is a GET HEAD call supposed to work when a proxy is in use by > the client? We had one caching proxy server that was returning > a 500, but the server is in beta and I kind of dismissed this > as the possible cause. I'm now seeing it at a customer's site, > and that makes me think this might be something systemic. > > John > > --------------------------------------------------------------- > John James Email: jjames@firstfloor.COM > First Floor, Inc. Web: http://www.firstfloor.COM > 444 Castro Street, Suite 200 Tel: (415) 254-5101 > Mountain View. CA 94041 Fax: (415) 968-1193 > > --- Gregory Woodhouse gjw@wnetc.com home page: http://www.wnetc.com/ resource page: http://www.wnetc.com/resource/ --- End Included Message --- --------------------------------------------------------------- John James Email: jjames@firstfloor.COM First Floor, Inc. Web: http://www.firstfloor.COM 444 Castro Street, Suite 200 Tel: (415) 254-5101 Mountain View. CA 94041 Fax: (415) 968-1193
Received on Thursday, 11 April 1996 16:56:59 UTC