Re: encryption madness

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 47153
interpreted = N
texte = >1) By using only a single URL in your purchase tag, you are getting the raw encrypted data written to the order file, as you have observed. The problem is that SOMETIMES the encrypt may result in characters that will mess up the order file formatting - like tabs or returns. Using a double-URL will prevent these problems by encoding the dangerous characters. Note that if you do double-URL the value, then you need to UNURL *INSIDE* the DECRYPT in order to get the original value back out (e.g. [decrypt seed=abc][unurl][accountnum][/unurl][/decrypt])Actually, encryption will never create tabs or returns just so it doesn't disrupt this file format or database files. Double URLing will still create percent signs and these really shouldn't be placed in the accountNum field.User a header field for the encrypted value, leave the accountNum field alone. Like Brian said, this leaves the door open to use WebMerchant at some point. -- --------------------------------- John A. Hill Oak Hill Software Website Development/Consulting john@oakhillsoftware.com------------------------------------------------------------- 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:

    
  1. Re: encryption madness ( Thierry Almy 2004)
  2. Re: encryption madness ( "Scott Anderson" 2004)
  3. Re: encryption madness ( Thierry Almy 2004)
  4. Re: encryption madness ( Squaredancer@t-online.de (Squaredancer) 2004)
  5. encryption madness ( Thierry Almy 2004)
  6. Re: encryption madness (John Hill 2003)
  7. Re: encryption madness (Kimberly D. Walls 2003)
  8. Re: encryption madness (Brian Fries 2003)
  9. Re: encryption madness (Kenneth Grome 2003)
  10. Re: encryption madness (John Hill 2003)
  11. Re: encryption madness (Kimberly D. Walls 2003)
  12. Re: encryption madness (Kenneth Grome 2003)
  13. Re: encryption madness (Kimberly D. Walls 2003)
  14. Re: encryption madness (Kimberly D. Walls 2003)
  15. Re: encryption madness (Kimberly D. Walls 2003)
  16. Re: encryption madness (Stuart Tremain 2003)
  17. Re: encryption madness (Brian Fries 2003)
  18. Re: encryption madness (Kenneth Grome 2003)
  19. Re: encryption madness (Stuart Tremain 2003)
  20. Re: encryption madness (Kenneth Grome 2003)
  21. Re: encryption madness (Donovan 2003)
  22. Re: encryption madness (Glenn Busbin 2003)
  23. Re: encryption madness (Andrew Simpson 2003)
  24. Re: encryption madness (Stuart Tremain 2003)
  25. Re: encryption madness (Tim Robinson 2003)
  26. Re: encryption madness (Andrew Simpson 2003)
  27. Re: encryption madness (Kimberly D. Walls 2003)
  28. Re: encryption madness (Glenn Busbin 2003)
  29. Re: encryption madness (Stuart Tremain 2003)
  30. Re: encryption madness (Rob Marquardt 2003)
  31. Re: encryption madness (Kimberly D. Walls 2003)
  32. Re: encryption madness (Kimberly D. Walls 2003)
  33. Re: encryption madness (Glenn Busbin 2003)
  34. Re: encryption madness (Bob Minor 2003)
  35. encryption madness (Kimberly D. Walls 2003)
>1) By using only a single URL in your purchase tag, you are getting the raw encrypted data written to the order file, as you have observed. The problem is that SOMETIMES the encrypt may result in characters that will mess up the order file formatting - like tabs or returns. Using a double-URL will prevent these problems by encoding the dangerous characters. Note that if you do double-URL the value, then you need to UNURL *INSIDE* the DECRYPT in order to get the original value back out (e.g. [decrypt seed=abc][unurl][accountnum][/unurl][/decrypt])Actually, encryption will never create tabs or returns just so it doesn't disrupt this file format or database files. Double URLing will still create percent signs and these really shouldn't be placed in the accountNum field.User a header field for the encrypted value, leave the accountNum field alone. Like Brian said, this leaves the door open to use WebMerchant at some point. -- --------------------------------- John A. Hill Oak Hill Software Website Development/Consulting john@oakhillsoftware.com------------------------------------------------------------- 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/ John Hill

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:

Re:Has this happened to you? (was:Emailer Chokes on bad address) (1997) creator code (1997) AND/OR searches in WebCat 3.07 (2003) textarea (2000) Database Options (1997) Moment of Thanks (1997) WebCat2b15MacPlugin - [protect] (1997) email messages (1997) Separate SSL Server (1997) Forcing Paragraph Breaks on Results (1998) verify email address (1998) RE: Adding headers to email (1997) japanese characters (1997) I forgot (1998) textA (1998) Banners (1997) Re:Emailer setup (1997) Comparing two fields so the match (1998) need e-commerce recommendation (2004) Multiple fields on 1 input (1997)