thanks everybody
On 1/24/07, Peter Schröder <[EMAIL PROTECTED]> wrote:
hi,
i remember a thread about encryption some time ago.
the essence of it was, that you send the parameters as is and add an encrypted
hash of your parameters with it, so that you can be sure nobody modified them.
thats a
If you're using Tapestry 4, friendly URL support could probably help you here.
Write a class that implements ServiceEncoder. Then implement decode(), where
you read your encrypted data and translate it to standard Tapestry parameters,
and encode(), where you do the reverse. Then apply the encode
Hi,
a custom encoder from the friendly-url guide
http://tapestry.apache.org/tapestry4.1/usersguide/friendly-urls.html
could be just as well used for unfriendly-urls
Michael
I want to encrypt (most of) the query string part of a tapestry webapp.
So instead of having an URL like..
http://lo
