setenv

Webserver in question is... /usr/sbin/apache2 -v Server version: Apache/2.4.7 (Ubuntu) Server built: Mar 10 2015 13:05:59 Portions of httpd.x.conf file... SSLVerifyClient optional SSLVerifyDepth 3 SSLOptions +StdEnvVars +ExportCertData SetEnvIf SSL_CLIENT_M_SERIAL "5174EAF60000000014E5" JK_REMOTE_USER=Rest But the result of that in the mod_jk.log is... [date and time junk] [debug] init_ws_service::mod_jk.c (1097): Service protocol=HTTP/1.1 method=GET ssl=true host=(null) addr=10.2.0.85 name=local.apiclient.com port=443 auth=(null) user=(null) laddr=10.2.1.173 raddr=10.2.0.85 uri=/the/thing/i

I'm looking for a solution, I can't pass to apache a variable define in /etc/profile. Here is what I am trying to set: I have a django application that I deploy through Apache/Passenger (modrails) through the WGSI interface. In my settings.py I am using this python command : ENVIRONMENT = os.getenv('ENV', 'PROD') so if the ENVIRONMENT variable is not define it goes to the production settings by default. That is helping me to manage which DB I connect to and activate debugging tools. It is working in production because it is the default values, it's when I am on the DEV server that I can't get

Is there anyway to use the value set in a SetEnv on the RewriteRule statement? Example: SetEnv MY_SCRIPT myScript.php rewriteEngine on RewriteRule ^(.*)$ %{MY_SCRIPT} [L] According to http://httpd.apache.org/docs/2.0/env.html the SetEnv is called after the RewriteRule. Therefore it seems to be impossible to use any variable set via SetEnv in a RewriteRule- or RewriteCond-statement. Using SetEnvIf on the other hand is called before the RewriteRule and therefore Variables set there can be used in a RewriteRule- or RewriteCond-statement. So something like the following should work: SetEnvIf

I'm using following in setenv to import the environment variable from where I run, but is there a way to import all the variables so that I don't really need to import one by one. e.g: {env:TEMPEST_CONFIG:} and {env:TEMPEST_CONFIG_DIR:} used to import these 2 variables. [testenv:nosetests] setenv = TEMPEST_CONFIG={env:TEMPEST_CONFIG:} TEMPEST_CONFIG_DIR={env:TEMPEST_CONFIG_DIR:} deps = {[testenv]deps} commands = find . -type f -name "*.pyc" -delete bash {toxinidir}/tools/setup.sh nosetests --with-xunit {posargs} You can use passenv . If you pass the catch all wildcard * you have access to all

I installed Zend on my ubuntu homeserver. In my .htaccess file i have the following code: SetEnv APPLICATION_ENV development RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-s RewriteCond %{REQUEST_FILENAME} !-l RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^.*$ index.php [NC,L] When i echo APPLICATION_ENV in my index.php in the public folder, APPLICATION_ENV is not set. What am i doing wrong? Mod rewrite is enabled in apache. In order to use SetEnv within a .htaccess file, I believe you need to set... AllowOverride FileInfo ...within the relevant virtualhost directory block. (And then

Is it possible to set a SetEnv variable in an .htaccess file differently depending on hostname? For example, I need my .htaccess file to have the following value: SetEnv PYRO_ENV production On production boxes, and... SetEnv PYRO_ENV stage On staging boxes. The .htaccess file is version controlled, which is the reason I'm looking for a conditional solution. Fabian Schmengler For conditional settings there is SetEnvIf : SetEnvIf Host ^stage\.example\.com$ PYRO_ENV=stage SetEnvIf Host ^(www\.)?example\.com$ PYRO_ENV=production You can, with mod_rewrite: RewriteEngine on RewriteCond %{HTTP_HOST}