DefaultHttpUtilities.getParameter gets headers, not parameters

[esapi]

DefaultHttpUtilities.getParameter gets headers, not parameters

[meg23]

From chrisisbeef on August 02, 2009 00:41:08

in every container I have worked with the getParameters will return the value
regardless of if they are POST or GET. Perhaps we should look creating a request
wrapper for HttpServletRequest that only returns parms for whatever method the
request was made using.

It definately begs an interesting question - If a form is submitted as a POST, but
someone submits a GET parameter with the same name, which one wins out and is
returned when I call getParameter

[meg23]

From [email protected] on October 26, 2009 23:40:29

The method now calls getParameter. We can add the POST/GET validation later if we
decide so.

Status: Started
Owner: neil.matatall
Labels: OpSys-All Usability

[meg23]

From [email protected] on November 09, 2009 05:39:34

Labels: -Priority-Medium Priority-High Component-Docs Component-Logic

[meg23]

From [email protected] on November 09, 2009 05:40:30

Labels: Milestone-Release2.1

[meg23]

From chrisisbeef on December 01, 2009 23:56:11

Please close out this issue and create a new enhancement request for POST/GET
validation for 2.1

[meg23]

From [email protected] on December 02, 2009 12:40:37

Status: Fixed
Labels: -Milestone-Release2.1

[Vaibs]

Its a pain when I have a huge JSON in POST and wants to validate using the ESAPI. Do we have anything concrete to validate a heavy json using ESAPI ?