- From: olga <olga@goliath.eai.com>
- Date: Thu, 14 Jan 1999 13:01:21 -0600 (CST)
- To: www-lib@w3.org
Hi, To stop request from processing I am returning value not equal to HT_OK from the before filter. In HTNet_newClient is causes the after filters to be called immediately. The problem is that my last after filter issues a new request (which can be stopped and after filter is then called and so on...). Normally HTNet_newClient would return to caller and after filters would be called from event loop when net object is cleaned. In my case HTAccess's functions just do not return and effectively after filters are called from inside HTAccess's functions. This causes stack to grow proportionally to how many requests in a row are stopped by before filters. (and it is a big number...) It there a safer way to stop request in before filters? It would be good if HTNet_newClient after getting the "NOT OK" value from before filters could 1) register some event that would cause the after filters to be called later 2) RETURN Is that possible? How to do that? I do not yet know the event management in w3c... :-( Thanks a lot, Olga Antropova.
Received on Thursday, 14 January 1999 13:57:43 UTC