HTTP keep-alive
[1/3] from: greggirwin::mindspring::com at: 12-Feb-2002 12:39
Hi Gang,
Is there an easy way to change the HTTP-get-header to use keep-alive,
instead of close, for its connection? Looking at the way the scheme is put
together, and not really being a net-cnetric guy to begin with, I didn't see
an obvious way.
Why do I want to do this? Well, I'm talking to a box that has a server built
into it and watching a couple other apps talk to it, I can see that they
have keep-alive on, but REBOL doesn't. I'm not sure it will solve my
problem, but if it's an easy thing to do, it's worth a shot.
Thanks!
--Gregg
[2/3] from: hallvard:ystad:helpinhand at: 13-Feb-2002 12:06
This works:
t: open/custom http://babelserver.com/ [header [Connection: "keep-alive"]]
...but when I say "works", I mean it makes an HTTP request with "Connection: keep-alive"
in the header, but where to go from there, I don't know. I pasted it into the Rebol console,
and it did keep-alive the connection, because I didn't get the prompt back without hitting
escape.
This probably didn't solve your problem, but I couldn't resist posting it anyway (finally
it's me helping Gregg, and not the other way around!).
~H
Dixit Gregg Irwin (20.39 12.02.2002):
[3/3] from: greggirwin:mindspring at: 13-Feb-2002 13:30
Thanks Hallvard!
<< This works:
t: open/custom http://babelserver.com/ [header [Connection: "keep-alive"]]
>>
That works for me. I can use it with read/custom in my case. I don't know
yet if it will solve my problem, but it does set keep-alive correctly!
--Gregg