Re[2]: Re[3]: Problem with new formvariables
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31227
interpreted = N
texte = Jesse - The only sensible level of security is one that you have to explicitly _opt outof_, not remember to enable. And the discussion at hand is not whethervariables defined within a template could be locked, but rather whethervariables passed as part of the command line could override variables on thetemplate.i.e. index.shtml?ipaddress=10.0.0.1 currently overrides the system variable [ipaddress], which is _highly_ insecure. This can be rightly considered to be a bugfix, not an upgrade.John Peacock____________________Reply Separator____________________Subject: Re: Re[3]: Problem with new formvariables Author:
Date: 5/2/2000 11:02 AMAre you saying that if you had:[text secure=t]SecureVar=T[/text][text]Securevar=f[/text]that the value would get to F? but it would be secure.The only way to change secure vars should be:[text secure=t]securevar=t[/text][text secure=t]securevar=f[/text] Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting#############################################################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 To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
Jesse - The only sensible level of security is one that you have to explicitly _opt outof_, not remember to enable. And the discussion at hand is not whethervariables defined within a template could be locked, but rather whethervariables passed as part of the command line could override variables on thetemplate.i.e. index.shtml?ipaddress=10.0.0.1 currently overrides the system variable [ipaddress], which is _highly_ insecure. This can be rightly considered to be a bugfix, not an upgrade.John Peacock____________________Reply Separator____________________Subject: Re: Re[3]: Problem with new formvariables Author: Date: 5/2/2000 11:02 AMAre you saying that if you had:[text secure=t]SecureVar=T[/text][text]Securevar=f[/text]that the value would get to F? but it would be secure.The only way to change secure vars should be:[text secure=t]securevar=t[/text][text secure=t]securevar=f[/text] Jesse Proudman - NineWire Productions http://www.ninewire.com <-> jesse@ninewire.com Innovative and Creative Web Design and Hosting#############################################################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 To switch to the INDEX mode, E-mail to Send administrative queries to
jpeacock@univpress.com
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:
WebCat odd log behavior (1998)
WebCat2final1 crashes (1997)
Hiding HTML and page breaks (1997)
[shownext] (1998)
100% CPU on NT (2001)
Fwd: search engine friendly URLS (Mac) (1998)
Advice needed. (1998)
Problems appending to database (1997)
Requiring that certain fields be completed (1997)
Replace with Producteditor.tpl (2000)
[WebDNA] Function and surviving variables (2016)
Online reference (1997)
Enterprise Server (1998)
Not really WebCat- (1997)
[BULK] [WebDNA] [BULK] [middle] behavior (2020)
Help!!!! (1999)
Need relative path explanation (1997)
PCS Emailer's role ? (1997)
Press Release hit the NewsWire!!! (1997)
empty shopping cart message (1997)