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:

Adding Shipping Fields (1999) Requiring that certain fields be completed (1997) Error: Error: expected [/APPLICATION] ??? (1998) A few questions. . . (1997) Another question (1997) Cookies and webcat (1997) can pull down menu do a ONCHANGE= without Java script? (2000) Tax on Shipping question (1998) SKU's (2000) F*** you (1998) More questions about serial number dishing (1997) wish list (2002) Searching multiple fields (1997) The USArea® Network web site ... (1997) WebDNA Quick Reference (Reserved Words) (2000) wild question (1998) select multiple (1997) Strange intermittent WebDNA problems (2008) Bad cookie (1998) RE: Error -108 (1997)