Re: Separating GET and POST parameters
Benjamin Kram <[email protected]> Wed, 3 Aug 2005 11:52:37 -0400
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
Jeremy,
These are all good coding practices. I typically check $r->method (or $ENV{REQUEST_METHOD}) to see the request method.
I typically have form pages that process their own arguments if they receive a POST.
cheers,
ben
> No way. I think there's some reasonable arguments for seperating them out;
> they are designed for different purposes.
>
> Examples:
> I might want to prevent someone from submitting their password via GET (less
> secure).
> I might want to prevent someone from submitting binary data via GET (very
> likely to be invalid).
> I might want to prevent someone from submitting a repeatable query (say, to
> a search engine) via POST (not bookmarkable).
--
"it would be horrid to be robbed
by the wrong kind of people"
-archy
Don Marquis, "the big bad wolf", 1935
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click