BNA doesn't use Internal Redirects in our code base. We didn't like the
log behavior. Your proposal to change the log behavior is an idea that I
agree with. Are you intending the 404 to appear in the log and then
execute the redirect page?
I agree with your thoughts on overriding all response codes, but it is a
feature that we don't really need given the way we build our code. If it
is as much hassle as your comments suggest, is it worth the effort?
/pgw
Dossy Shiobara <[EMAIL PROTECTED]> wrote
> #
> # Internal redirects
> #
> ns_section "ns/server/${servername}/redirects"
> ns_param 404 "/notfound.html" ;# Not Found error page
> ns_param 500 "/servererror.html" ;# Server Error page
>
> 1) Allow overriding of all response codes. This may not actually be a
> good idea, but it just seems odd that only certain response codes
> have their own C API which uses the internal redirect mechanism.
>
> I'm still on the fence whether #1 is a good idea or not. In principle
> it's the right thing to do, but implementing it properly will require a
> lot of refactoring of nsd/return.c to make it clean, and even then
> there could be problems.
>
> Thoughts? Problems?
>
> -- Dossy
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
