in reply to Reason to use GET vs POST? (discussion)

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...

  • Comment on Re: Reason to use GET vs POST? (discussion)