Bug 31484 - Custom environment variables not passed to content negotiated resources
Summary: Custom environment variables not passed to content negotiated resources
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_negotiation (show other bugs)
Version: 2.0.52
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://test.io.link-m.de/apache2/env+...
Depends on:
Reported: 2004-09-30 11:31 UTC by Julian Mehnle
Modified: 2017-12-18 20:12 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Julian Mehnle 2004-09-30 11:31:37 UTC
When I enable content negotiation using "Options MultiViews", and I try to
access a resource without its full name (i.e. without filename extensions), only
a certain set of environment variables is available to the resource.  Some
Apache-defined variables and any custom-defined (through SetEnv) variables are
NOT available to the resource.  This applies to SSI resources as well as to CGI

Try accessing
and look the for custom-defined variable "__FOO__".  It should have the value

Now try accessing
and you will see that the "__FOO__" variable and some others (predefined by
Apache) are missing.

The same goes for
http://test.io.link-m.de/apache2/env+content_negotiation/test-cgi.pl  and

Look at the .txt resources to see the source code of test-ssi.shtml and
test-cgi.pl.  Look at the apache2.conf and vhost.conf resources to see the
Apache and vhost configuration.

I'm not sure whether this is a mod_negotiation or a mod_env bug.
Comment 1 Joergen Thomsen 2005-01-14 16:35:28 UTC
The request variables (POST and GET) are not passed either. This is a bug in 
mod_negotiation, which was solved in the Apache1 version in 2001. I saw it 
somewhere in the bugs archive, but the (very simple) source change cannot just 
be applied to the Apache2 module, as the source has changed much.
Comment 2 Joergen Thomsen 2005-01-14 16:56:59 UTC
Just search the archives and find a bunch of error reports of the same problem, 
which should have been fixed in Apache 1.3.23

Comment 3 Nick Kew 2017-12-17 09:22:55 UTC
What a brilliant bug report, with test links that are still valid today!

The test links show that the reported bug is indeed fixed in the server version now in use.
Comment 4 Julian Mehnle 2017-12-18 20:12:03 UTC
Agreed, it seems to be fixed. Glad it's working now!