From: simonxy on
Hi,

I have IIS 7.0. I created a custom http module. In module I use beginn
request event and I'm checking some rules.
Sometimes(depends on rules) I just send some short response to the
client and end the execution. I would like also to close the
connection on IIS. In performance monitor I see, tahat it stays open
for 60 seconds. After that it closes.
Can I close connection immediatelly after sending a response?

Thank you for your answer,
Simon
From: Chris M on
On 17/03/2010 08:41, simonxy wrote:
> I have IIS 7.0. I created a custom http module. In module I use beginn
> request event and I'm checking some rules.
> Sometimes(depends on rules) I just send some short response to the
> client and end the execution. I would like also to close the
> connection on IIS. In performance monitor I see, tahat it stays open
> for 60 seconds. After that it closes.
> Can I close connection immediatelly after sending a response?

Try turning off HTTP KeepAlives - although bear in mind that Keepalives
are a benefit on busy sites because the client doesn't need to create a
new connnection for each subsequent request, therefore removing some of
the overhead.

--
Chris M.
From: simonxy on
On Mar 17, 10:10 am, Chris M <nob...(a)nowhere.special> wrote:
> On 17/03/2010 08:41, simonxy wrote:
>
> > I have IIS 7.0. I created a custom http module. In module I use beginn
Thank you for your answer. I already found a solution. If I send conn
close in response, it works.
The point is that there wont be subsequent request because this
requests come from DOS attacks.

regards, S
From: simonxy on
On Mar 17, 10:10 am, Chris M <nob...(a)nowhere.special> wrote:
> On 17/03/2010 08:41, simonxy wrote:
>
> > I have IIS 7.0. I created a custom http module. In module I use beginn
Thank you for your answer. I already found a solution. If I send conn
close in response, it works.
The point is that there wont be subsequent request because this
requests come from DOS attacks.

regards, S