Thanks for your reply.

After tinkering with it a bit more, I was able to figure out what was
causing it to hang on a POST command, although I'm still not sure exactly
why.  I had a FTOSV filter setup to remove several headers (User-Agent and
Referer), and when I removed the filter, POST worked great.

I'm also having a similar hanging problem with https.  If I have the proxy
setup as the proxy in my browser, I can load https pages through it with
no problems.  However, when I try loading them through
http://proxy-server/-_-https://secure-web-site/, it hangs until the
browser times out.  If you need me to provide any logs or system-specific
information in regards to this, let me know.

Thanks for your help.

On Sun, 29 Aug 1999, Yutaka Sato wrote:

> On 08/28/99(02:04) you CJB <pgibabdyi-qa4rnugeboa6.ml@delegate.org> wrote
> in <_A562@delegate-en.ML_>
>  |I have a fairly standard DeleGate setup (no special options, just a
>  |standard HTTP proxy), and so far it seems to be working great except when
>  |I try to submit a form that uses POST.  When I attempt to do so, DeleGate
>  |seems to hang, and eventually my browser times out after "Waiting for
>  |reply..." for several minutes.  Further testing to one form revealed that
>  |it took around 7 minutes before the post request finally went through.  I
>  |have tried it in Internet Explorer 5, Lynx 2.8.1pre9, and Netscape 4.07,
>  |all with the same results.
>  |
>  |Is there something obvious in the setup that I'm missing, or is anyone
>  |aware of any bugs relating to this?  Any help anyone can offer would be
>  |greatly appreciated.
> 
> I don't know a setup with which I can make DeleGate hang on POST method,
> and I've not heard a problem about POST with recent version of DeleGate.
> Thus I'd like to hear followings to figure out what is the problem:
> 
>  - your setup
>  - the version of your DeleGate
>  - the OS you are using
>  - what kind of data you posted (show me the URL if you could)
>  - the log data of DeleGate around POST is waiting to be relayed
> 
> The following is an example of log data of DeleGate relaying a POST request.
> 
> 08/29 15:38:42.82 [691] 1+0: -- Fork(SequentialServer): 690 -> 691
> 08/29 15:38:42.83 [691] 1+1: (0) accepted [12] -@[xx.xx.xx.xx]client-host:3951 (0.010s)(1)
> 08/29 15:38:42.84 [691] 1+1: Proxy: host=client-host; User-Agent: Mozilla/3.01Gold [ja] (Win95; I); DIRECT
> 08/29 15:38:42.84 [691] 1+1: HCKA:[0] Keep-Alive; host=client-host; (User-Agent: Mozilla/3.01Gold [ja] (Win95; I))
> 08/29 15:38:42.84 [691] 1+1: REQUEST = POST http://www/path HTTP/1.0^M
> 08/29 15:38:42.84 [691] 1+1: PATH> http://www:80!yslina:8080!client-host:3951!anonymous@client-host;935908722
> 08/29 15:38:42.85 [691] 1+1: REQUEST = [http://www/] POST /path HTTP/1.0^M
> 08/29 15:38:42.89 [691] 1+1: ConnectToServer connected [8] {www:80 <- client-host:1104} [0.039s]
> 08/29 15:38:42.89 [691] 1+1: HTTP => (www:80) POST /path HTTP/1.0^M
> 08/29 15:38:42.89 [691] 1+1: relayRequestBody1 done (56/54)
> 08/29 15:38:43.43 [691] 1+1: HTTP/1.0 200 Content-{Type:text/html Encoding:[/] Leng:285} Server:CERN/3.0pre5
> 08/29 15:38:43.46 [691] 1+1: Content-Length: 285 -> 285 (547 - 262)
> 08/29 15:38:43.62 [691] 1+1: HTTP transmitted: 239head+285/285body=>0txt+0bin->285/285, 8i/2o/0f/0.7
> 08/29 15:38:43.63 [691] 1+1: HCKA:[0] closed -- M:Method is ``POST'' cpid=[0]
> 08/29 15:38:43.63 [691] 1+1: disconnected [12] -@[xx.xx.xx.xx]client-host:3951 (0.806s)(0)
> 
> Cheers,
> Yutaka
> --
> Yutaka Sato <ysato@etl.go.jp> http://www.etl.go.jp/~ysato/   @ @ 
> Computer Science Division, Electrotechnical Laboratory      ( - )
> 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan            _<   >_
>