Thanks, but I was more so looking to find out if there was some sort of formal spec that the mod_ssl team used to decide what SSL environment variables to create. I am making some changes to stunnel to support http proxying and I wanted to include some headers for user CGIs. Since I can not find any spec, describing what SSL environment variables are expected, I have simply chosen to insert the headers X-Https and X-Session-Id.
Thus spake Colin Faber, on the year of our L*rd Wed, Aug 20, 2003 at 05:32:58PM -0600: > Dumping the environment variables is a very simple task. Try: > > > #!/bin/sh > echo "Content-type: text/plain" > echo "" > /usr/bin/printenv > > > chmod it and stick it on your SSL server and run it. > > > Philip Champon wrote: > > >Hi, > > > >I tried searching the archives, to find out where I might be able > >to read about a CGI/SSL spec, but I couldn't turn anything up? > >While I have read the mod_ssl ref on envirionment variables, I was > >hoping to find out what source the group used to compile this list > >of environment variables. I also consulted the CGI spec, but it did > >not cover any SSL specific variables. > > > >Could someone tell me, is there such a spec, or did the group arbitrarily > >compile a list of SSL env vars to include in the CGI env? > > > > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] -- Philip Champon Affinity Developer Ph - 954-334-8156 Em - [EMAIL PROTECTED] ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
