Depending on how you're using the XSL, Cocoon->XQuery->XSL is one option -
although I don't know how Xquery would get access to your environment
variables directly.  But you could use XQuery to stream the values into the
source XML as nodes just like the rest of your data, then deal with them how
you please in the XSL.  You can use an XQuery module to store the variables
in question and import them into whatever XQueries you write.

The problem with this approach is that it locks you into a webapp
architecture that you might not want to deal with, though I'd be curious to
hear recommendations for non-Cocoon implementations of XQuery for webapps.

-Andy

> 
> On Fri, Jun 19, 2009 at 3:44 PM, Doran, Michael D <[log in to unmask]> wrote:
> 
>> I am working with some XSL pages that serve up HTML on the web.  I'm new to
>> XSL.   In my prior web development, I was accustomed to being able to access
>> environment variables (and their values, natch) in my CGI scripts and/or via
>> Server Side Includes.  Is there an equivalent mechanism for accessing those
>> environment variables within an XSL page?
>> 
>> These are examples of the variables I'm referring to:
>>    SERVER_NAME
>>    SERVER_PORT
>>    HTTP_HOST
>>    DOCUMENT_URI
>>    REMOTE_ADDR
>>    HTTP_REFERER
>> 
>> In a Perl CGI script, I would do something like this:
>>    my $server = $ENV{'SERVER_NAME'};
>> 
>> Or in an SSI, I could do something like this:
>>    <!--#echo var="REMOTE_ADDR"-->
>> 
>> If it matters, I'm working in: Solaris/Apache/Tomcat
>> 
>> I've googled this but not found anything useful yet (except for other
>> people asking the same question).  Maybe I'm asking the wrong question.  Any
>> help would be appreciated.
>> 
>> -- Michael
>> 
>> # Michael Doran, Systems Librarian
>> # University of Texas at Arlington
>> # 817-272-5326 office
>> # 817-688-1926 mobile
>> # [log in to unmask]
>> # http://rocky.uta.edu/doran/
>> 
>>