There is a new filter point for ns_register_filter called prequeue.
It isn't very useful because it runs in the driver thread, blocking the loop
until it finishes with all prequeue filters that match. (There may actually
be spins wasted on every request looking for matches, haven't checked
So I'm guessing noone else had this issue? Seems like filters are hosed.
--Tom Jackson
Tom Jackson wrote:
I am running a minimum current checkout of AOLserver. My init.tcl file
has the following:
proc myfilter { } {
ns_return 200 text/plain Hi there
return filter_return
}
ns_register_filter
Sorry I didn't really read this sooner. I've got a preauth filter in my
4.0b2 setup, and it's working fine. I notice you declared your filter
with no arguments, but I declared mine with this:
proc some_filter { args } {
Maybe it doesn't like being declared as having no arguments? Mine
Yes, got that, I took it out to test what the effect would be. But I did
just verify that now when you have an incorrect number of arguments to a
filter, AOLserver just logs the error and closes the connection. I'll
check into the exact bug here. Must be a return code that is being over
used.
Hello,
I'm trying to use ns_register_filter, and am running into difficulties.
I have the following code in an init.tcl:
ns_register_filter postauth GET /*/bob mqa.processHostedRequest
ns_register_filter postauth POST /*/bob mqa.processHostedRequest
mqa.processHostedRequest looks like
On 2003.02.17, Ross Simpson [EMAIL PROTECTED] wrote:
I'm trying to use ns_register_filter, and am running into difficulties.
That's because you want to use ns_register_proc, not ns_register_filter.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer
You want filter_return instead of filter_break
filter_break just stops running filters and continues with the connection
On Monday 17 February 2003 02:41 pm, Ross Simpson wrote:
Hello,
I'm trying to use ns_register_filter, and am running into difficulties.
I have the following code in an
Dossy,
The problem with ns_register_proc is that it expects the requested file
to exist -- something I don't want. I want a proc run for any request
matching a pattern, and after that proc runs, for the connection to be
closed.
David Walker's post about returning filter_return seems to have
On Mon, 17 Feb 2003, Ross Simpson wrote:
The problem with ns_register_proc is that it expects the requested file
to exist -- something I don't want.
No it doesn't.
On 2003.02.17, Ross Simpson [EMAIL PROTECTED] wrote:
The problem with ns_register_proc is that it expects the requested file
to exist -- something I don't want. I want a proc run for any request
matching a pattern, and after that proc runs, for the connection to be
closed.
That's strange --
Dossy wrote:
On 2003.02.17, Ross Simpson [EMAIL PROTECTED] wrote:
The problem with ns_register_proc is that it expects the requested file
to exist -- something I don't want. I want a proc run for any request
matching a pattern, and after that proc runs, for the connection to be
closed.
I think you are putting the register filter commands in nsd.tcl, but
nsd.tcl is a startup file and only certain commands are allowed.
Instead, create a .tcl file with your register filter commands and
procedures, and put that file in servername/modules/tcl
Jim
Hi.
I'm trying to map user
12 matches
Mail list logo
