What’s the difference between POST and PUT? Simply put (ha), think of a POST as asking a server to perform some operation on the specifed data vs. In your analysis, you may also come across the HTTP PUT.
A search request is a good example of this. Note that for simple submissions were there are only a few variables, parameter(s) passed to the GET method will suffice. Another good example is submitting the content of web-based email when you click the send button. A POST is typically used to submit the content of a form or to post a message. In a nutshell, a POST is telling the server to accept information and perform an operation in the context of the resource identified in the URI. Since this is one of the few blogs that actually compares some of the finer points when it comes to expert systems from various vendors, I’ll touch on how some of the analyzers handle HTTP POST analysis.īut first let’s look at the basic HTTP POST operation.
Perhaps for that reason we don’t understand it as well when it comes to analyzing its behavior.Įven the tool vendors (anything that collects a packet, even if it’s not a protocol analyzer per se) often blow off the importance of this vital HTTP operation, leaving us scratching our heads to figure out where the problem is with our web-based applications. The POST method is a distant second behind GET in terms of popularity. The HTTP POST is a method or operation that the server is to perform on the resource as identified by the Uniform Resource Identifier (URI). After all, when a user of a browser-based application clicks on a button or presses the enter key, shouldn’t they expect a quick reply?
The Random House Unabridged Dictionary defines post haste as "with the greatest possible speed or promptness: to come to a friend's aid posthaste." I thought this was fitting when analyzing HTTP POST traffic.
0 kommentar(er)
