troublesome at sign

[Leslie MacNeill]

I'm trying to put an email address into a token. The @ keeps converting to its hex code: %40, then every time the token is carried to the next page, the % also converts to its hex code %25, so eventually I end up with %25252540 when it should just be an @.

I would like to try inserting the &___; code for it initially to see if that solves the problem, but I can't find it anywhere (I can find the ampersand code for just about everything else but that). Does anyone know it?

Or does anyone have any other ideas on how to solve this problem?

[Martin Brändle]

I would never ever pass an e-mail address in a token, i.e. in an URL - this is a high security risk because the URL can be spoofed, e.g. somebody can enter another address and abuse your mailing system.

Use a field or a session for passing the address to the next page.

Anyway, when you pass a value in an URL, you can encode it with

fmxslt:url_encode()

and decode it on the next page with

fmxslt:url_decode()

Edited September 5, 2006 by Guest

[abassin]

Can you elaborate with some code examples?

I am interested in learning more techniques for securing email transmissions. I have built a login db which uses the users email as the username. So I am using their email to pass to my find query in xsl. How can I avoid this?

Edited September 9, 2006 by Guest