Can you provide more details of your architecture?
Think of threads while trying to understand things like that.
Once a thread is started to execute something it will go throught its life
cicle and then die.
Probably your container is doing something via a thread.
Does it make sense?
Siomara
-----Original Message-----
From: Glenn Wearen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 05, 2001 12:14 PM
To: [EMAIL PROTECTED]
Subject: Browser stop buttons
I've noticed that my JSP container continues to process my request even
after I have pressed my browsers STOP button.
This seems to be a security weakness, since a two year old could launch a
DoS attack on my JSP container.
Does anybody know the cause of this? or how would you tell the container to
stop processing the request after the STOP button was pressed?
Glenn Wearen
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets