Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

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

by shotgunefx (Parson)
on Sep 18, 2001 at 03:21 UTC ( [id://113010]=note: print w/replies, xml ) Need Help??


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

The only POST attack I can really think of is posting huge chunks of data to try and fill the filesystem where the processing program is storing it. The only remotely relavent vunerablility I know of is the Cross Protocol Scripting vunerability which in my opinion would be a bad reason to disable POSTs altogether.

-Lee

"To be civilized is to deny one's nature."
  • Comment on Re: Reason to use GET vs POST? (discussion)

Replies are listed 'Best First'.
Re: Re: Reason to use GET vs POST? (discussion)
by Hero Zzyzzx (Curate) on Sep 18, 2001 at 03:35 UTC

    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.

      I agree. I can't imagine they disabled it in the source.

      -Lee

      "To be civilized is to deny one's nature."

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://113010]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (3)
As of 2024-04-24 04:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found