Evuraan wrote:
<ngrep start> T 192.168.1.103:17670 -> 192.168.1.100:80 [AP] POST /evuraan/formtest/code.shtml HTTP/1.1. Via: <someproxy> Cookie: <SNIP> Referer: <snip> Content-Type: application/x-www-form-urlencoded. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10. Host: <snip> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8. Accept-Language: en-us,en;q=0.5. Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7. Keep-Alive: 300. Connection: Keep-Alive. Content-Length: 21. . first=BLAH_ONE&second=BLAH_TWO # # T 192.168.1.100:80 -> 192.168.1.103:17670 [AP] HTTP/1.1 200 OK. </ngrep end> While I agree POST data format can get way too complex, I am lamenting @ the simple fact that there is no param like POST_DATA or POST_STRING which simply would mean: POST_DATA="first=BLAH_ONE&second=BLAH_TWO" or POST_STRING="first=BLAH_ONE&second=BLAH_TWO" from a simple POST which I sniffed as shown above.
Ok, true. The format depends on the "enctype" attribute of the <form>. By default, and for non-file type of fields, it is a you show above. I was thinking only of the multipart/form-data type. (Try <form ... enctype="multipart/form-data"> to see what I meant)Well then, you should just be able to read the body of the POST, and do the parsing yourself.
If you are running a cgi script, the body should just be on its STDIN. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|