Reason to use GET vs POST? (discussion)by deprecated (Priest)
|on Sep 18, 2001 at 02:58 UTC ( #113000=perlquestion: print w/replies, xml )||Need Help??|
deprecated has asked for the wisdom of the Perl Monks concerning the following question:
I have been hassling with apple's bundled apache that comes with OS X Server. Its a run-of-the-mill 1.3.19 with a ton of extension to deal with everything from Apple's use of HFS+ (vs a case-sensitive file system) to their JSP stuff.
Anyhow, I spent several hours earlier today figuring out what was wrong with a script of mine. Turns out Apple saw fit to disable POST entirely, and my forms must use GET instead.
The reasoning for this totally boggles me. I cant think of any reasons, security or otherwise, for doing this. Has anyone got any ideas why they would do this?
update:i checked the <limit> tags, fixed the config file, and indeed it appears that POST has been disabled in the source. This is very irritating to the point I will be installing a separate apache instance on this box.
Back to Seekers of Perl Wisdom