Re: [WebDNA] Encode cookies ONLY via "method=Base64"

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 109288
interpreted = N
texte = This is a multi-part message in MIME format. --------------090105070400040505010303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit WOW! Talk about a blast-from-the-past-thread! I saw my name in there and had to go digging into the 2008 archives! -Matt On 7/13/2012 3:19 AM, Stuart Tremain wrote: > Almost 4 years on and the only encryption/decryption that you can do > with cookies is method=Base64, and I have just spent 2 days proving it :( > > Thinking of opening a liquor store ..... problem is it may be like > Dracula in charge of the Blood Bank > > > > > On 28/10/2008, at 1:42 PM, Stuart Tremain wrote: > >> On 28/10/2008, at 1:11 PM, Kenneth Grome wrote: >> >>> Hi Matthew, >>> >>> I tested WebDNA and learned that it won't produce [math] >>> results more than 15 chars long before it resorts to >>> scientific notation, and therefore it appears your >>> suggestion is not possible ... :( >>> >>> I also did a bunch of reading online about prime numbers >>> (very interesting) but none of it matters for use in WebDNA >>> if the [math] context cannot produce numbers more than 15 >>> chars long. >>> >>> It sure would be nice if encrypt / decrypt worked with >>> cookies, and I'm not sure why it doesn't when it works with >>> db's. Any theories about this? >>> >>> Sincerely, >>> Ken Grome > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------090105070400040505010303 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit WOW!  Talk about a blast-from-the-past-thread!
I saw my name in there and had to go digging into the 2008 archives!

-Matt


On 7/13/2012 3:19 AM, Stuart Tremain wrote:
Almost 4 years on and the only encryption/decryption that you can do with cookies is method=Base64, and I have just spent 2 days proving it :(

Thinking of opening a liquor store ..... problem is it may be like Dracula in charge of the Blood Bank




On 28/10/2008, at 1:42 PM, Stuart Tremain wrote:

On 28/10/2008, at 1:11 PM, Kenneth Grome wrote:

Hi Matthew,

I tested WebDNA and learned that it won't produce [math]
results more than 15 chars long before it resorts to
scientific notation, and therefore it appears your
suggestion is not possible ... :(

I also did a bunch of reading online about prime numbers
(very interesting) but none of it matters for use in WebDNA
if the [math] context cannot produce numbers more than 15
chars long.

It sure would be nice if encrypt / decrypt worked with
cookies, and I'm not sure why it doesn't when it works with
db's.  Any theories about this?

Sincerely,
Ken Grome

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 


-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & EducatorPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------090105070400040505010303-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2012)
  2. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2012)
  3. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime Inc, Matthew A Perosi " 2012)
  4. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Govinda 2012)
  5. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2012)
  6. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  7. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  8. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  9. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  10. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  11. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  12. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  13. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  14. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Gary Krockover" 2008)
  15. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  16. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  17. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Marc Thompson 2008)
  18. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Bob Minor 2008)
  19. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2008)
  20. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Marc Thompson 2008)
  21. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Patrick McCormick 2008)
  22. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  23. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Brian Fries 2008)
  24. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Christer Olsson 2008)
  25. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  26. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Donovan Brooke 2008)
  27. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  28. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  29. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  30. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  31. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  32. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  33. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2008)
  34. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Bob Minor 2008)
  35. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  36. RE: [WebDNA] Encode cookies ONLY via "method=Base64" ("Olin Lagon" 2008)
  37. RE: [WebDNA] Encode cookies ONLY via "method=Base64" ("Olin Lagon" 2008)
  38. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  39. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  40. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  41. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  42. Re: [WebDNA] Encode cookies ONLY via "method=Base64" ("Psi Prime, Matthew A Perosi " 2008)
  43. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
  44. Re: [WebDNA] Encode cookies ONLY via "method=Base64" (Stuart Tremain 2008)
  45. [WebDNA] Encode cookies ONLY via "method=Base64" (Kenneth Grome 2008)
This is a multi-part message in MIME format. --------------090105070400040505010303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit WOW! Talk about a blast-from-the-past-thread! I saw my name in there and had to go digging into the 2008 archives! -Matt On 7/13/2012 3:19 AM, Stuart Tremain wrote: > Almost 4 years on and the only encryption/decryption that you can do > with cookies is method=Base64, and I have just spent 2 days proving it :( > > Thinking of opening a liquor store ..... problem is it may be like > Dracula in charge of the Blood Bank > > > > > On 28/10/2008, at 1:42 PM, Stuart Tremain wrote: > >> On 28/10/2008, at 1:11 PM, Kenneth Grome wrote: >> >>> Hi Matthew, >>> >>> I tested WebDNA and learned that it won't produce [math] >>> results more than 15 chars long before it resorts to >>> scientific notation, and therefore it appears your >>> suggestion is not possible ... :( >>> >>> I also did a bunch of reading online about prime numbers >>> (very interesting) but none of it matters for use in WebDNA >>> if the [math] context cannot produce numbers more than 15 >>> chars long. >>> >>> It sure would be nice if encrypt / decrypt worked with >>> cookies, and I'm not sure why it doesn't when it works with >>> db's. Any theories about this? >>> >>> Sincerely, >>> Ken Grome > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator Psi Prime, Inc. 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------090105070400040505010303 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit WOW!  Talk about a blast-from-the-past-thread!
I saw my name in there and had to go digging into the 2008 archives!

-Matt


On 7/13/2012 3:19 AM, Stuart Tremain wrote:
Almost 4 years on and the only encryption/decryption that you can do with cookies is method=Base64, and I have just spent 2 days proving it :(

Thinking of opening a liquor store ..... problem is it may be like Dracula in charge of the Blood Bank




On 28/10/2008, at 1:42 PM, Stuart Tremain wrote:

On 28/10/2008, at 1:11 PM, Kenneth Grome wrote:

Hi Matthew,

I tested WebDNA and learned that it won't produce [math]
results more than 15 chars long before it resorts to
scientific notation, and therefore it appears your
suggestion is not possible ... :(

I also did a bunch of reading online about prime numbers
(very interesting) but none of it matters for use in WebDNA
if the [math] context cannot produce numbers more than 15
chars long.

It sure would be nice if encrypt / decrypt worked with
cookies, and I'm not sure why it doesn't when it works with
db's.  Any theories about this?

Sincerely,
Ken Grome

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 


-- Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & EducatorPsi Prime, Inc.323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://www.perosi.com
--------------090105070400040505010303-- "Psi Prime Inc, Matthew A Perosi "

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:

Timer Values on [redirect] (1998) [WebDNA] PROTECT (2017) question: search return in order (1997) AppleScript question (1997) [item] appears after 'remove last item' ... (1997) Re:2nd WebCatalog2 Feature Request (1996) text size limitation (1997) Nesting FoundItem Context (1997) Gremlins, huh? (2000) can WC render sites out? (1997) [WriteFile] problems (1997) suggestion (1997) creating a ShipCosts database (1997) Merging databases (1997) Archive (Zip, Sit, Tgz) (2004) Reversed words (1997) ShipCosts database (1997) [lookup] speed sales pitch (2003) WebCat2b15MacPlugin - showing [math] (1997) autocommit problem (1998)