W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 2001

Re: Update on PUT Corruption, question on HTTP version setting

From: Niklas Wiberg <e95_nwi@it.kth.se>
Date: Wed, 28 Feb 2001 18:25:10 +0100
To: Bob Schader <bobs@product-des.com>
Cc: Www-Jigsaw <www-jigsaw@w3.org>
Message-ID: <3A9D3476.788F25D3@it.kth.se>
An observation that I did a while ago is that the squid proxy has a
setting described below. It could be some restriction like that you're
running into IF there is a transparent proxy in between. (Although the
error isn't the same...)
I can't see why your ISP would impose such a restriction though...

Quoted from the squid.conf file:
#  TAG: request_body_max_size	(KB)
#	This specifies the maximum size for an HTTP request body.
#	In other words, the maximum size of a PUT/POST request.
#	A user who attempts to send a request with a body larger
#	than this limit receives an "Invalid Request" error message.
#	If you set this parameter to a zero, there will be no limit
#	imposed.

--Niklas

Bob Schader wrote:
> 
> After reading the spec, I am going to try commenting
> out the request.setExpect("100-continue") call I have
> in my program and see what happens then.
> Bob
> _____________________________
> Bob Schader
> CAD Systems Admin
> Product Design Intl., Inc.
> 4880 36th St. SE, Suite 100
> Grand Rapids, MI 49512
> (616) 667-2600 x104
> 
> -----Original Message-----
> From: www-jigsaw-request@w3.org [mailto:www-jigsaw-request@w3.org]On
> Behalf Of Bob Schader
> Sent: Wednesday, February 28, 2001 8:04 AM
> To: Www-Jigsaw
> Subject: Update on PUT Corruption, question on HTTP version setting
> 
> I am beginning to think I am the victim of "transparent proxy"
> syndrome. I did some test PUT's to the localhost on the problem
> system and they worked fine. Then I did some searching on the net
> for info about these proxies.
> 
> I found some info that suggested I could resolve the majority of
> problems caused by transparent proxies by changing the registry
> settings for MTU and TCP Window size. After adjusting these settings,
> I was able to successfully upload the 180K test file I had been
> trying to upload previously, and it was not corrupted.
> 
> However, then I tried uploading a file that was over 2MB and everthing
> seemed to go fine, but when it finished, I got a HTTP/1.1 417
> Expectation Failed error in the reply and the file was not even saved
> on the server. I haven't had a chance yet to look up what the
> meaning of that error yet, but I have reached another conclusion
> that I am interested in trying out.
> 
> All the other programs I haved used successfully for PUT's did them
> as "HTTP/1.0", while I see that Jigsaw's client library defaults
> to HTTP/1.1. Looking thru the source, I found references for setting
> the request type in HttpBasicServer, using either the field
> RQ_HTTP10_KA (or RQ_HTTP10, no keep-alive) and the method
> HttpBasicServer.http10_ka_run(request). Is this something I
> can set when using the HttpManager methods to setup my request
> so I can tell it to use HTTP/1.0? My needs don't really require
> a 1.1 version at this point, so I would like to try it.
> 
> Bob Schader
> 
> _____________________________
> Bob Schader
> CAD Systems Admin
> Product Design Intl., Inc.
> 4880 36th St. SE, Suite 100
> Grand Rapids, MI 49512
> (616) 667-2600 x104
Received on Wednesday, 28 February 2001 12:26:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:35 GMT