Re: Accessing Server Environment Variables
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 49101
interpreted = N
texte = John,Thanks for the suggestion. Until we have an explicit WebDNA context for retrieving environment variables, you can use the DOS context to grab that information.Here is an example using the new WebDNA 5 function context...[function name=GetEnvironmentVar] [listwords words=[DOS]Set [/DOS]&delimiters=[unurl]%0D[/unurl]] [showif [url][middle startafter=&endbefore==][word][/middle][/url]=[url][params_string][/url]] [return][middle startafter==&endbefore=][word][/middle][/return] [/showif] [/listwords] [/function]Examples:
CLASSPATH = [GetEnvironmentVar CLASSPATH]
OS = [GetEnvironmentVar OS]
SystemRoot = [GetEnvironmentVar SystemRoot]
etc...This could easily be adapted to work with earlier versions of WebDNA. > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > John Peacock > Sent: Tuesday, April 01, 2003 2:32 PM > To: WebDNA Talk > Subject: RFE: Accessing Server Environment Variables > > > The more recent versions of WebSite support custom error > handling, with a single > file being able to handle multiple error states. In order to > create a custom > 404 message in WebDNA, I need to be able to access the server > environment > variables, in order to see the original path that was requested. > > For example, in Perl I would call > > $original_path = $ENV{'4XX_PATH'}; > > but WebDNA does not support this. > > I'd like new contexts that would work much like the > [ListMIMEHeaders] and > [GetMIMEHeader] tags; I propose [ListENVVariables] and > [GetENVVariable]. These > contexts would return the server environment variables for > later processing. > This feature is available in both for Windows and *nix web > servers (I cannot > speak to classic Mac, but that is being discontinued). > > Thanks > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
John,Thanks for the suggestion. Until we have an explicit WebDNA context for retrieving environment variables, you can use the DOS context to grab that information.Here is an example using the new WebDNA 5 function context...[function name=GetEnvironmentVar] [listwords words=[DOS]Set [/DOS]&delimiters=[unurl]%0D[/unurl]] [showif [url][middle startafter=&endbefore==][word][/middle][/url]=[url][params_string][/url]] [return][middle startafter==&endbefore=][word][/middle][/return] [/showif] [/listwords] [/function]Examples:
CLASSPATH = [GetEnvironmentVar CLASSPATH]
OS = [GetEnvironmentVar OS]
SystemRoot = [GetEnvironmentVar SystemRoot]
etc...This could easily be adapted to work with earlier versions of WebDNA. > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > John Peacock > Sent: Tuesday, April 01, 2003 2:32 PM > To: WebDNA Talk > Subject: RFE: Accessing Server Environment Variables > > > The more recent versions of WebSite support custom error > handling, with a single > file being able to handle multiple error states. In order to > create a custom > 404 message in WebDNA, I need to be able to access the server > environment > variables, in order to see the original path that was requested. > > For example, in Perl I would call > > $original_path = $ENV{'4XX_PATH'}; > > but WebDNA does not support this. > > I'd like new contexts that would work much like the > [listmimeheaders] and > [getmimeheader] tags; I propose [ListENVVariables] and > [GetENVVariable]. These > contexts would return the server environment variables for > later processing. > This feature is available in both for Windows and *nix web > servers (I cannot > speak to classic Mac, but that is being discontinued). > > Thanks > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Scott Anderson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebCatalog for guestbook ? (1997)
Rép : Old & New? (2003)
multiple search commands (1997)
Requiring that certain fields be completed (1997)
Problems adding stuff to the shopping cart. (1997)
Removing [showif] makes a big difference in speed (1997)
Performance tuning WebCat on NT (2000)
Banners and sort of random display (1997)
apostrophe in search item (1997)
Does anyone have any ideas? (2007)
looping table rows (1999)
Sorting by date (1997)
Help Wanted - Stowe, Vermont (1999)
Search over 500 (2000)
Too Much Info (1998)
Quiestion (1997)
Closing databases (2003)
ooops...WebCatalog [FoundItems] Problem - LONG - (1997)
WebCatalog 2.0 b 15 mac (1997)
Choices (2000)