comment on

Are you sure that it's totally disabled? Look at the <LIMIT> statements in your httpd.conf file, this is where you set whether or not a location can accept GET or POST requests.

That truly sucks if you can only use GET. It's not more secure, but it's the only way to send largish amounts of data (like a file upload) to your script. . .

If you're only going to do vanilla stuff, it's pretty easy to recompile apache, though I have no idea how this works on OS X

-Any sufficiently advanced technology is
indistinguishable from doubletalk.

In reply to Re: Re: Reason to use GET vs POST? (discussion) by Hero Zzyzzx
in thread Reason to use GET vs POST? (discussion) by deprecated

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks