Re: CommandSecurity?

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 12636
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?There's no username or password fields in this database, there's only 3 fields - newssku, newsdate and newstext.Aah ... but I have the page protected with my custom WebDNA ... so the browser already has username and password values cached before I try to use this page. Could it be that when the browser already has a cached value for username and password, the replace or delete won't work unless I either:1- create username and password fields in the database to compare the browser's values against, or ...2- put &username=[username]&password=[password] into the context?If that's all it is, this is a HUGE misunderstanding on my part!I thought I didn't have to put &username=[username]&password=[password] into replace or delete contexts or forms or urls unless there were fields in the database with exactly the same names.Was I wrong about this?Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html 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?There's no username or password fields in this database, there's only 3 fields - newssku, newsdate and newstext.Aah ... but I have the page protected with my custom WebDNA ... so the browser already has username and password values cached before I try to use this page. Could it be that when the browser already has a cached value for username and password, the replace or delete won't work unless I either:1- create username and password fields in the database to compare the browser's values against, or ...2- put &username=[username]&password=[password] into the context?If that's all it is, this is a HUGE misunderstanding on my part!I thought I didn't have to put &username=[username]&password=[password] into replace or delete contexts or forms or urls unless there were fields in the database with exactly the same names.Was I wrong about this?Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html 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:

One more try (1997) date sorting and 'template (1997) WebDNA 6.0a for Apache 2.2.4 (2007) Forms Search Questions (1997) [WebDNA] New list (2008) Sku numbers (1997) dates and hex formatting (1997) TeaRoom Order fields email account remain empty even though thewy are filled. (1997) [OT] Getting a domain listening on port 443 and port80? (2003) [WebDNA] Screen Resolution - detection & redirect (2012) PCS Frames (1997) shoppingcart reload qty (1997) can WC render sites out? (1997) Email within tmpl ? (1997) WebCatalog 4.0.2b5 available (2000) proper way to check if a container is empty? (2000) still having shipCost.db Problem (1997) Just Testing (1997) [WebDNA] current thinking on architecture of mass email scripts? (2011) [OT] Certs (2002)