Hidden fields are not more secure than parameters in the URL.
('show source' in your browser and everything is revealed...)
But they look more 'professionnal' to me, even if I admit it's purely subjective and aesthetic...
To me one way to secure a parameter would be to compute a hash (MD5,SHA1)
of the parameter, the id session, and a private value
(the customer ref in your base, for example)
This way the link can't be cut and pasted later (beccause of the ID session)
And link can't be faked given an id-session
(as the private value is needed to compute the hash...)
UPDATE :
Just my 2 cents idea, Cookies would solve a lot of your troubles here,
a lot of professionnal sites use them.
And you may be surprised to see how well the customers accept this constraint
('Yes sir! your browser need to be cookie enabled to use our site.'
is a sentence that I often say and it's always ok for my customers...)
"
Only
Bad
Coders
Badly
Code
In
Perl" (OBC2IP)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.