In response to an HTTP POST I am performing a

response.setHeader("Connection", "close");

My JRun4 is configured with IIS.  I think this used to work, but perhaps
something else has changed (did browsers always use Keep-Alive on
POSTs?).  It is currently not working - for a couple months now, and IIS
overrides this with a "Connection: Keep-Alive" - which is what the
browser requests.  Browser (IE and NS) requests are coming into my
server as POSTs, and their connections are staying open and not
closing.  This creates a problem for my application in situations where
IE or NS only want to have two concurrent socket connections open - I am
using one of those two for a dedicated, persistent connection on a
custom app.

If I configure JRun to run using it's webservice and bypass IIS my app
runs as designed.

I have used the sniffer program provided with JRun to verify that the
setHeader() call is not working.

Help or pointers would be appreciated to make this call work with the
JRun connector for IIS.

Thanks, BenG.
--
Ben Groeneveld,
bgroeneveld [at] communicast [dot] com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to