The only thing I can think of that would explain why you may have a drop for the post method would be if you were wanting to prevent a post to the server. There is a good tutorial on the different html methods here: http://www.jmarshall.com/easy/http/#othermethods It says:
A POST request is used to send data to the server to be processed in some way, like by a CGI script. A POST request is different from a GET request in the following ways: - There's a block of data sent with the request, in the message body. There are usually extra headers to describe this message body, like * Content-Type:* and *Content-Length:*. - The *request URI* is not a resource to retrieve; it's usually a program to handle the data you're sending. - The HTTP response is normally program output, not a static file. Anyhow, you can read....but if you wanted to make sure that nobody could POST to the ACS you would drop and log it. But---the lab never asks for it so you can leave it out. HTH. -- Brandon Carroll, CCIE #23837 GlobalConfig.net PO Box 267 Mercer Island, Wa 98040 ph. (206) 866-5750 email: [email protected] on the web: www.globalconfig.net On Sat, May 23, 2009 at 4:02 PM, Paul Stewart <[email protected]> wrote: > I am trying to understand where in lab 1a that it states something that > would prompt dropping and logging "post" requests to the ACS server. Am I > overlooking it somewhere? Honestly that is quite possible. >
