Re: [AOLSERVER] ns_register_filter problem: proc not found AOLserver HEAD
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 preauth GET /* myfilter
When I connect to / I get no return from the server at all, it just
closes the connection. The error log shows
that the proc myfilter is not found. (Also Mozilla on RH8.0 seems to try
the connection 7 or so times because of the
disconnect)
--Tom Jackson
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
Re: [AOLSERVER] ns_register_filter problem: proc not found AOLserver HEAD
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 is
running on a RH 8.0 box.
Pete.
On Mon, 3 Mar 2003, Tim Moss wrote:
We'll try this on our RH8.0 box tomorrow and will let you know the outcome
ASAP.
-Original Message-
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 preauth GET /* myfilter
When I connect to / I get no return from the server at all, it just
closes the connection. The error log shows
that the proc myfilter is not found. (Also Mozilla on RH8.0 seems to try
the connection 7 or so times because of the
disconnect)
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
Re: [AOLSERVER] ns_register_filter problem: proc not found AOLserver HEAD
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. Maybe I should also register the trace and see if that still
fires. Okay did that,
the trace filter doesn't fire either.
--Tom Jackson
Peter M. Jansson wrote:
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 is
running on a RH 8.0 box.
Pete.
On Mon, 3 Mar 2003, Tim Moss wrote:
We'll try this on our RH8.0 box tomorrow and will let you know the outcome
ASAP.
-Original Message-
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 preauth GET /* myfilter
When I connect to / I get no return from the server at all, it just
closes the connection. The error log shows
that the proc myfilter is not found. (Also Mozilla on RH8.0 seems to try
the connection 7 or so times because of the
disconnect)
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
Re: [AOLSERVER] ns_register_filter problem
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 Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] ns_register_filter problem
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 done the trick. Thanks guys! Ross On Mon, 2003-02-17 at 14:12, Dossy wrote: 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 Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] ns_register_filter problem
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.
Re: [AOLSERVER] ns_register_filter problem
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 -- I use ns_register_proc for URLs where the document the URL refers to /definitely/ do not exist in the pageroot. Weird. David Walker's post about returning filter_return seems to have done the trick. That'll work, too. Cool. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] ns_register_filter problem
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. That's strange -- I use ns_register_proc for URLs where the document the URL refers to /definitely/ do not exist in the pageroot. Weird. Filters work the same as procs in that respect, since they are based on the url, not what exists under pageroot. However, only one proc can be registered for any url, so when that proc fires, the request is considered served, and the process moves on to run any trace filters. The fastpath proc is registered on /* for methods GET, POST, HEAD, so if you don't register anything more specific, the fastpath proc will pick up the request processing. The steps involved in a request are: 1. run all preauth filters that match the url pattern in the order they were registered during startup, or until any filter returns filter_break or filter_return 2. auth request unless filter_return returned above, 3. same as 1 for postauth filters unless a preauth filter returned filter_return 4. run closest matching registered proc, assuming filter_return was not returned 5. run any trace filters unless one returns filter_return or filter_break --Tom Jackson
Re: [AOLSERVER] ns_register_filter
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 home directories /home/user/public_html as http://server/~user. Thanks to Jeff Putsch I have a Tcl script that does that. I'm using AOLServer 3.3.1 and the error I get is that the command ns_register_filter is not found. Can I replace that command with something else or what should I do ? Thanks a lot - Carmen
