Alvaro Lopez Ortega wrote:
This is close to what I need, however I cannot setup a 404 error
handler to trap scgi get involved. I search the mail archive a bit,
without much success. Any suggestion on this matter? What's the
equivalent of server.error-handler-404 in lighttpd?
That is one of the worst ideas I have ever seen. IMO, the error
redirection is mechanism shouldn't be used in such a messy way.
Let's check your configuration and I bet we'll come up with some
good solution. :-)
as one of the other creators of "worst 404 error handler ever", let me
say again that I think that both models are valid because it depends on
how you look at the Web serving world. If you take the view grounded in
the 90s and look at the 404 handler as strictly an error handling
mechanism, and yes what should only use it to display a static or semi
static page saying what you did wrong.
The if on the other hand you view access resolution (i.e. URL
translation to some action) as exception handling, then it makes sense
to be able to have an exception hierarchy. For example,
find the file?: return it
exception
|
V
program exist?: execute a program
exception
|
V
...
default "I'm out of options" handler.
I haven't seen 0.6 so I don't know how the configuration works but the
current version looks awfully close to this. If one could express a
handlehandler list, then the user could create this kind of access
resolution logic based on their needs. You can even get rid of combined
and just have users do file; directory.
anyway, just a thought.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
