Eric S. Johansson wrote:
PHP is the sendmail (in terms of security) of the Web set. ;-)
LOL! ;-) Well, I think the problem is some the web programmers, not the language.
like I said...
I'm not 100% sure about it, but what you seem to want to use is PathInfo with an internal rewriting rule. Let me explain myself; imagine a configuration like this:
Directory /program { Handler cgi DocumentRoot /usr/lib/cgi-bin/program }
If you request http://host/program/cgi, it will reply with the CGI output, but if you request http://host/program/cgi/param1 it _will_ send the "/param1" argument to the CGI and reply with the value of the execution of it with that parameter. You don't need an error handler to manage things like that. :-)
true
Try some configuration like this with the 0.4.21 release (I'm going to upload it in a few minutes), I hope it will work for your case:
DirectoryIndex /yourcgi.xxx
Extension xxx { Handler cgi }
Directory / { Handler file }
hmm. I was thinking more like
directory / { handler CGI /path/to/CGI
}or
directory / { handler CGI /path/to/CGI
run /path/to/CGI
}on the other hand, if Python were embedded, I wouldn't object. ;-)
the ability to log X-Forwarded-for: addresses in place of the upstream proxy address.
I don't understand this requirement. What do you want to do with that header?
I have multiple web sites on a couple different machines sitting behind a single IP address. I redirect based on name-based virtual domains using pound. normally access logs just show the proxy address which is not very useful. But since Pound uses the X-Forwarded-for: header for telling downstream servers where the request really came from, it would be nice to use it in the logs. Obviously, one must be extremely careful in doing so since it can be forged. The usual solution is to put in ACL that require you to specify the proxy to treat as authoritative.
Could you please send me a couple of that headers as example. That feature seems to be interesting for the next release.
here is what I know ----------------------- http://www.apsis.ch/pound/
REQUEST LOGGING
As a general rule, Pound passes all headers as they arrive from the client browser to the back-end server(s). There are two exceptions to this rule: Pound may add information about the SSL client certificate (as described below), and it will add an X-Forwarded-For header. The general format is:
X-Forwarded-for: client-IP-address
The back-end server(s) may use this extra information in order to create their log-files with the real client address (otherwise all requests will appear to originate from Pound itself, which is rather useless).
In addition, Pound logs requests and replies to the system log. This is controlled by the LogLevel configuration variable (0 - no logging, 1 - normal log, 2 - full log, 3 - Apache combined log format, 4 - Apache combined log format without virtual host).
By default the messages go to the LOG_DAEMON facility, but you can change this in the configuration. If you don't want to, you can just do a:
fgrep pound /var/log/messages
to get all the messages generated by Pound.
and other words, if I do it, you'll take the change. :-)
Great :-)
D'oH!
that would be helpful. Thanks for the feedback. If I can find a way to make things were the way I want regarding aether, it sounds like the switch would be worth it.
We should be able to make that work right with Cherokee. :)
sounds grand.
---eric
-- http://www.wired.com/wired/archive/13.03/view.html?pg=5
The result of the duopoly that currently defines "competition" is that prices and service suck. We're the world's leader in Internet technology - except that we're not. _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
