Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: GET and POST Methods Accepted

Subject: Re: GET and POST Methods Accepted
Date: Thu, 13 Oct 2005 10:03:42 -0000 (GMT)

This is not the case.  The HttpServlet class defines separate methods
for each HTTP request.  So there is a doGet() and a doPost() method
to handle forms and the container will direct the request to the
appropriate method.  The developer would have to purposefully make
them interchangeable by calling doPost() from within the doGet()
method, or visa-versa.  See: http://java.sun.com/products/servlet/2.1/
servlet-2.1.pdf for more info on the spec.


You're right. I take that back.  What I was thinking about was the spec
requires that POST parameters in the body be treated the same way as
parameters in the URL, even though the HTTP spec doesn't specify how POST
parameters should be encoded.

<Prev in Thread] Current Thread [Next in Thread>