Stefan de Konink wrote, On 01/12/2007 20:55: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > I'm very annoyed by the behavior of Cherokee especially by its way to > frustrate sysops with not working rewrites. Is there a way to debug or > SEE where a rewrite goes to?
There are two kinds of redirections: internal and client redirections. The best thing that you can do is to set the redirections by using client redirections and then, if you want them to be internal (hidden from the client: the browser URL would not change) just remove the "show" option. There are a few examples about the Cherokee 0.5 configuration files format: http://www.cherokee-project.com/doc/Redirections.html Anyway, there is another trick that you could use in Cherokee 0.6-beta. The new tracing facility will be quite useful in this case. You will need to compile the server with the --enable-trace parameter, and then launch the server with the CHEROKEE_TRACE environment variable. For instance: CHEROKEE_TRACE=all /usr/sbin/cherokee to trace everything, or in the case you want only the redir info: CHEROKEE_TRACE=redir /usr/sbin/cherokee -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
