[0xDEAD10CC]

If a shell (bleh) you're using has a form to submit, you can use a GET or POST request through a WebClient to not have this ridiculous code.

Submissions would be a POST request, if it's by link, then you would use a GET request.

[Shebang]

Submissions would be a POST request, if it's by link, then you would use a GET request.

I've seen some forms that make the request through GET by generating the GET link. I guess it's a bad implementation though.

[0xDEAD10CC]

But a submit button is typically used for POSTing data, if it is a GET, it's typically just a link

[IcanFLY]

Why are people still posting on this thread?

[xornull]

ps this method does not use UDP
it will usually result in use of HTTP which uses TCP.

so faku

[0xDEAD10CC]

ps this method does not use UDP
it will usually result in use of HTTP which uses TCP.

so faku

He's using a WebBrowser to navigate to a PHP script. How do you assume that the PHP script is using the TCP protocol? :S There is no flooding with the WebBrowser, so the assumption to make here is that the PHP script is somehow responsible for doing that instead (PHP doesn't have to use TCP).

[xornull]

He's using a WebBrowser to navigate to a PHP script. How do you assume that the PHP script is using the TCP protocol? :S There is no flooding with the WebBrowser, so the assumption to make here is that the PHP script is somehow responsible for doing that instead (PHP doesn't have to use TCP).

Perhaps, even so, why would it not use TCP? No decent web developer should use UDP for something that doesn't need better performance [It is also prone to IP spoofing].

[0xDEAD10CC]

What is the risk here though with UDP over TCP? Remember the application it's being used for here. A flooder doesnt need better performance?