Re: URL'ed value not written to DB URL'ed
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53554
interpreted = N
texte = >He was saying that if you wanted the actual URLized value to appear in the >db (ie. Hi%20Mom) then you would need to double Urlized. Oh, sorry. I thought he was saying that there are situations that actually require it, not that it's just an option. Most people would not want the data urled in the db because that creates search problems. >Encrypting values to be store in a db. Putting encrypted values in a *single* url context in an append or replace tag is good enough. You don't have to double-url the encrypted value. These code snippets come directly from the WebCatalog Engine/Admin/Security folder and they illustrate that double-urling is not necessary when storing encrypted values in a db: ConfirmAppend.tpl: [append Users.db]...&pass=[url][encrypt][uppercase][pass][/uppercase][/encrypt][/url]...[/append] ConfirmSetPass.tpl [replace db=Users.db&equserdata=[uppercase][user][/uppercase]]pass=[url][encrypt][uppercase][pass][/uppercase][/encrypt][/url][/replace] -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>He was saying that if you wanted the actual URLized value to appear in the >db (ie. Hi%20Mom) then you would need to double Urlized. Oh, sorry. I thought he was saying that there are situations that actually require it, not that it's just an option. Most people would not want the data urled in the db because that creates search problems. >Encrypting values to be store in a db. Putting encrypted values in a *single* url context in an append or replace tag is good enough. You don't have to double-url the encrypted value. These code snippets come directly from the WebCatalog Engine/Admin/Security folder and they illustrate that double-urling is not necessary when storing encrypted values in a db: ConfirmAppend.tpl: [append Users.db]...&pass=[url][encrypt][uppercase][pass][/uppercase][/encrypt][/url]...[/append] ConfirmSetPass.tpl [replace db=Users.db&equserdata=[uppercase][user][/uppercase]]pass=[url][encrypt][uppercase][pass][/uppercase][/encrypt][/url][/replace] -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
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:
Subtotal help (1997)
[WebDNA] Middle Question (2015)
Emailer error 571 (1998)
Funny Chars (1999)
Web Catalog vs. ICAT (1997)
Shipping.db (1998)
Hideif on IP range (2004)
service stop and restart (1997)
WebCat chatroom/hyperboard (1997)
OS X permissions to write to Globals directory (2003)
Encrypting Credit Card Numbers (2004)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Supressing Error Messages (1998)
Silly Question (1997)
[OT] Display Glitch (2004)
Single Link browsing (1997)
Email Not Being Sent (2004)
[OT] Industry news from Australia (2000)
Re:Emailer and encryption (1997)
emailer settings and control questions (1997)