New Command prefs ...
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10341
interpreted = N
texte = Okay, so ...If commandSecurity=F, then there is no command security used by WebCat2 whatsoever, and anyone can type any WebCat2 $command they wish into a web browser, and WebCat2 will perform that command ... right?And it really makes no difference what's typed into the CommandsAllowed pref when commandSecurity=F because the CommandsAllowed pref is ignored when commandSecurity=F ... right?But when commandSecurity=T, that's when WebCat2 actually looks at the commands in the CommandsAllowed pref ... right?And when commandSecurity=T and WebCat2 finds a particular command in the CommandsAllowed pref (such as Replace, for example) then it tells WebCat2 to continue to allow that command to be executed from a URL, even though that URL might have been typed into a remote browser ... right?But when the CommandsAllowed pref does *not* have a particular command in the CommandsAllowed pref (such as Append, for example) then anytime someone attempts to do an Append from a URL, the append will fail ... right?From my understanding, a command typed into the URL or Location field of a web browser will look exactly the same to WebCat2 as an identical command that someone has preformatted and placed into a hyperlink ... right?So, if I use hyperlinks on my website to execute preformatted commands, I do *not* want to leave those commands out of the CommandsAllowed pref list - or the commands I leave out will no longer work from my hyperlinks ... right?Sincerely, Ken
Associated Messages, from the most recent to the oldest:
Okay, so ...If commandSecurity=F, then there is no command security used by WebCat2 whatsoever, and anyone can type any WebCat2 $command they wish into a web browser, and WebCat2 will perform that command ... right?And it really makes no difference what's typed into the CommandsAllowed pref when commandSecurity=F because the CommandsAllowed pref is ignored when commandSecurity=F ... right?But when commandSecurity=T, that's when WebCat2 actually looks at the commands in the CommandsAllowed pref ... right?And when commandSecurity=T and WebCat2 finds a particular command in the CommandsAllowed pref (such as Replace, for example) then it tells WebCat2 to continue to allow that command to be executed from a URL, even though that URL might have been typed into a remote browser ... right?But when the CommandsAllowed pref does *not* have a particular command in the CommandsAllowed pref (such as Append, for example) then anytime someone attempts to do an Append from a URL, the append will fail ... right?From my understanding, a command typed into the URL or Location field of a web browser will look exactly the same to WebCat2 as an identical command that someone has preformatted and placed into a hyperlink ... right?So, if I use hyperlinks on my website to execute preformatted commands, I do *not* want to leave those commands out of the CommandsAllowed pref list - or the commands I leave out will no longer work from my hyperlinks ... right?Sincerely, Ken
Kenneth Grome
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:
Re:Hideif / Showif (1998)
Embedded [Search] Context Snippets (Very Useful) (1998)
PROBLEM (1997)
New Guestbook Source (1997)
Word Break (1999)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
Quit revisited (1997)
[Sum] function? (1997)
OT - royalty free images (2002)
Help name our technology! (1997)
RE: [isfolder] and [filename] (1997)
Thanks ! (1997)
Applescript, WebDNA, and PDF (1997)
shared_POP and archiving your own mailing list (2003)
Number date (2006)
RE: AccountAuthorizer doesn't seem to work (1997)
WebCat2.0 [format thousands .0f] no go (1997)
Simple way to create unique SKU (1997)
RE: E-mailer error codes (1997)
WebMerchant problem (1998)