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

Update on PUT Corruption, question on HTTP version setting

From: Bob Schader <bobs@product-des.com>
Date: Wed, 28 Feb 2001 08:03:56 -0500 (EST)
To: "Www-Jigsaw" <www-jigsaw@w3.org>
Message-ID: <HFEMINDGIADFIPHHOLOGIEPECBAA.bobs@product-des.com>
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 09:37:35 GMT

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