encrypting without "ugly" URLs

This WebDNA talk-list message is from

2005

It keeps the original formatting. numero = 60841
interpreted = N
texte = I need to hide a few fields in a URL and have been using the encrypt context to do this.Of course the [url] contexts are required to make the result of the [encrypt] context usable in a URL. But the result is something like this:somepage.tpl?hiddenstuff=%25A6%25DE%2588%25A5%25A5%257D%25CF%25F3%25DE%250E%2580%2515%25C6%25F6ZT%251E3%2502%251E%25067%25BE%25A6which you have to admit is pretty ugly.So toying with method=apop I find that the result of the above [encrypt] is 7cfd82f4bc90641f864999d6579fe662and the result of method=base64 the result is ZmllbGQxPW9uZSZmaWVsZDI9dHdvboth of those appear to be plain ASCII character strings and therefore not "ugly"I know that I loose the [encrypt] ability to make each instance of a webcatalog [encrypt] be unique but that's not too terrible in this application.Can anyone verify that method=apop or method=base64 will always yield ascii strings?Thanks,~joe-- _______________________________________________________________ Joseph D'Andrea ~ http://www.west21.com/ ~ JoeDan@West21.com WEST21.com Internet services for the 21st Centurywebhosting ~ co-location ~ wireless access ~ WebCat programming-------------------------------------------------------------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:

Re: encrypting without "ugly" URLs ( John Peacock 2005)
Re: encrypting without "ugly" URLs ( Joe D'Andrea 2005)
Re: encrypting without "ugly" URLs ( John Peacock 2005)
Re: encrypting without "ugly" URLs ( John Peacock 2005)
encrypting without "ugly" URLs ( Joe D'Andrea 2005)

I need to hide a few fields in a URL and have been using the encrypt context to do this.[url][url][encrypt seed=joe]field1=one&field2=two[/encrypt][/url][/url]">Of course the [url] contexts are required to make the result of the [encrypt] context usable in a URL. But the result is something like this:somepage.tpl?hiddenstuff=%25A6%25DE%2588%25A5%25A5%257D%25CF%25F3%25DE%250E%2580%2515%25C6%25F6ZT%251E3%2502%251E%25067%25BE%25A6which you have to admit is pretty ugly.So toying with method=apop I find that the result of the above [encrypt] is 7cfd82f4bc90641f864999d6579fe662and the result of method=base64 the result is ZmllbGQxPW9uZSZmaWVsZDI9dHdvboth of those appear to be plain ASCII character strings and therefore not "ugly"I know that I loose the [encrypt] ability to make each instance of a webcatalog [encrypt] be unique but that's not too terrible in this application.Can anyone verify that method=apop or method=base64 will always yield ascii strings?Thanks,~joe-- _______________________________________________________________ Joseph D'Andrea ~ http://www.west21.com/ ~ JoeDan@West21.com WEST21.com Internet services for the 21st Centurywebhosting ~ co-location ~ wireless access ~ WebCat programming-------------------------------------------------------------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/ Joe D'Andrea

DOWNLOAD WEBDNA NOW!

encrypting without "ugly" URLs

2005

Top Articles:

Related Readings: