That's the thing with HTTP Multi-part Post - some little details count extremely much while others are disregarded, so unless you want to learn the standard by heart, you have to be painfully careful to replicate the browser request properly. And unfortunately there are no general solutions, you just have to take it step by step. I had a combination of multi-part posts and rfc "conflicting" with the way i designed the requests, and took me ages to get it working in all situations i needed them too.
On Fri, Jul 29, 2011 at 12:05 PM, sasidharsmit <sasidhars...@gmail.com>wrote: > At last, got a solution for this. > > Andrey, > As you had mentioned in your earlier POST, I was comparing the Wireshark > monitors for JMeter and HTTPRequestor. > > Everything was same, except that my JMeter request had a "Malformed Packet: > GIF Image" in the HTTP section. > > So, I compared the HTTP section and found that there is a single difference > between these two requests: > > The difference was "\r\n" (i.e.) one extra line space. So, instead of > having > a double line space between the header and the body, in JMeter, I used a > single line space and .... voila!!....it worked! :-D > > So, everything works fine now. > > *Solution:* Use a single empty line space between the Headers and the body. > > Thanks for your support, Andrey. > > Cheers, > Sasi > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/jp-gc-HTTP-Raw-Request-for-POST-requests-tp4635060p4646304.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
