Re: locking variables?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 28849
interpreted = N
texte = >So there is no way to prevent someone from overriding a variable just >by passing it via GET?You can use [FormVariables] at the top of the page to examine which variables are being overridden by the incoming GET, and put up an error message or redirect back to the same page without those particular form variables. We realize the current behavior is not optimal, and we're revisiting it for 4.0.Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- 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 Associated Messages, from the most recent to the oldest:

    
  1. Re: locking variables? (Kenneth Grome 2000)
  2. Re: locking variables? (Charles Kline 2000)
  3. Re: locking variables? (WebDNA Support 2000)
  4. Re: locking variables? (Glenn Busbin 2000)
  5. Re: locking variables? (Charles Kline 2000)
  6. Re: locking variables? (Jereme Claussen 2000)
  7. Re: locking variables? (Glenn Busbin 2000)
  8. Re: locking variables? (Kenneth Grome 2000)
  9. Re: locking variables? (Kenneth Grome 2000)
  10. Re: locking variables? (WebDNA Support 2000)
  11. Re: locking variables? (Jereme Claussen 2000)
  12. Re: locking variables? (Kenneth Grome 2000)
  13. Re: locking variables? (John Butler 2000)
  14. Re: locking variables? (WebDNA Support 2000)
  15. Re: locking variables? (Kenneth Grome 2000)
  16. locking variables? (Jereme Claussen 2000)
>So there is no way to prevent someone from overriding a variable just >by passing it via GET?You can use [formvariables] at the top of the page to examine which variables are being overridden by the incoming GET, and put up an error message or redirect back to the same page without those particular form variables. We realize the current behavior is not optimal, and we're revisiting it for 4.0.Technical Support ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive, #380 | ------------------------- San Diego, CA 92127 | Software & Site Development WebCatalog Support: (858) 675-0632 | http://www.smithmicro.com Fax: (858) 675-0372 **********************************------------------------------------------------------------- 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 WebDNA Support

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:

WC2.0 Memory Requirements (1997) Text data with spaces in them... (1997) How reliable is WebDNA? (2004) gateway application timeouts (1998) Weird problems with [SHOWIF]s (1997) [isfolder] and [filename] (1997) Whoops... meant to send it to her directly ... !!!! WebCatProgrammer Opening for Growth eCommerce Startup !!!! (1999) [OT] DOD again *MYSTERY SOLVED* (2003) Searching an Email database (1997) FYI: virus alert (1996) Extended [ConvertChars] (1997) setting values (1998) search for all (1998) Pithy questions on webcommerce & siteedit (1997) UPS charges (2000) AutoCommit Preference? (1998) Problems with [Applescript] (1997) Automatic thumbnail images (1998) OS X and cart directories (2003) Weird happenings (1998)