This would be very annoying if it's really turned off and not just disabled in the config file.

At my site I take in POSTs with more than the max GET size allowed by the browsers, so a loss of POST functionality would make those forms break. Probably silently as well.

GET has the other feature of cluttering up your log files with hoards of data that is being saved anyway. (the content of the form submission)

So from a logging and feature fullness standpoint, I think POST has to be allowed for the Web Server to use.

Of course with the Development CD you can get the C compiler and build an apache which will POST...

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.