Re: CommandSecurity?

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12634
interpreted = N
texte = >I removed Replace and Delete from the CommandsAllowed preference ... while >leaving CommandSecurity=T. > >I did this in an effort to 'shut off' all commands performed by forms and >URL's ... but it also seems to prevent context commands from working too. I >had to make CommandSecurity=F to get replace and delete to work without >adding them to the CommandsAllowed pref ... but setting CommandSecurity=F >completely eliminates all command security, right?I see nothing in the code that would prevent embedded contexts such as [Delete] or [Replace] from working regardless of what the CommandSecurity setting is. CommandSecurity is only for $(command) remote URL-style commands.Are you sure you've got the right passwords for those embedded contexts you're using?Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: CommandSecurity? (Grant Hulbert 1997)
  2. Re: CommandSecurity? (Kenneth Grome 1997)
  3. Re: CommandSecurity? (Kenneth Grome 1997)
  4. Re: CommandSecurity? (Grant Hulbert 1997)
  5. CommandSecurity? (Kenneth Grome 1997)
  6. CommandSecurity? (Kenneth Grome 1997)
>I removed Replace and Delete from the CommandsAllowed preference ... while >leaving CommandSecurity=T. > >I did this in an effort to 'shut off' all commands performed by forms and >URL's ... but it also seems to prevent context commands from working too. I >had to make CommandSecurity=F to get replace and delete to work without >adding them to the CommandsAllowed pref ... but setting CommandSecurity=F >completely eliminates all command security, right?I see nothing in the code that would prevent embedded contexts such as [delete] or [replace] from working regardless of what the CommandSecurity setting is. CommandSecurity is only for $(command) remote URL-style commands.Are you sure you've got the right passwords for those embedded contexts you're using?Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

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:

Form based Redirect (2001) [delete] problem (2002) Possible Bug in 2.0b15.acgi (1997) $Quit, $CloseDatabase corrections (1997) Re:Problem displaying search result (1997) One more try: WebCat for Dummies p2.2 (2000) Founditems context returning only 1 item (1997) Duplicate Hell (1999) Retaining data (2003) WebCat on OS X 10.4.7 won't send emails (2006) Smith Micro - no competition (2000) WCS Newbie question (1997) textarea inputs and returns (1999) UPS uber integration (2007) Multiple Newcarts (1996) Emailer setup (1997) Using Plug-In while running 1.6.1 (1997) Multiple Purchase (2002) WebCat for Site Search? (1997) [WriteFile] problems (1997)