Environment once more
Martijn Grendelman <martijn-FwI+/[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, At the risk of being flamed for asking the obvious, I'd like to go down the path of FastCGI application environment once more. I have spent the better part of yesterday searching and reading about environment variables and the ways they can and cannot be used with Apache and mod_fastcgi. I am using FastCGI with PHP and suExec. PHP is started through a wrapper script, that has to make some decisions (which php.ini to use, among others) based on the virtual host it is running for, before exec'ing PHP. Is there _any_ way to pass this kind of information from Apache to the wrapper script? I know SetEnv, PassEnv and the like won't cut it, and with -initial-env, I can only pass data from Apache's environment, which is useless to me. Would it be hard, or would there be any drawbacks, or unacceptabel security implications to have the FastCGI process manager set up an environment based on Apache's mod_env before it forks? I am not a C programmer, so there's no way I can implement this myself. I have seen similar questions in the list archives many times, and IMHO it's understandable that people want to be able to do this. Have I missed anything? Thanks, Martijn. ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/
smime.p7s
(application/x-pkcs7-signature, 3.2 KB) - not displayed