https://issues.apache.org/bugzilla/show_bug.cgi?id=46112

           Summary: POST with multi-part form doesn't work
           Product: JMeter
           Version: 2.3.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTTP
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


In 2.3.2, new functionality was added to support multi-part form with post.

This functionality does not work in 2.3.2 with a multi-part form file upload.

Both recording with the http proxy, and the actual test plan does not work with
this configuration.

It appears that the 8bit encoding is the issue.

That is each form field posting gets these 2 lines

Content-Type: text/plain; charset=iso-8859-1 
Content-Transfer-Encoding: 8bit 

When I test with a browser, and sniff the traffic, and my app works, these 2
attributes are not present.

I have not found a workaround using jmeter.properties.

I took my 2.3.2 test plan, and ran in 2.2 and my plan works.  In 2.2, only 1
file could be uploaded, and the new multi-part form post option did not exist,
but the plan works with 2.2 and not in 2.3.2.  

It appears either the content type and/or content-transfer-encoding is causing
the test plan to not work in 2.3.2.

Interestingly enough, in 2.3.2, the tree results viewer considers the call a
success, but that is only because of a 200 return code, but no result shows up
in the response part, and the files uploaded are not received on the server
end.

I found this issue on other web posts...here is one that shows the same type of
encoding I am seeing.

http://www.nabble.com/Problem-with-the-JMeter-HTTP-Proxy-td19435675.html


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to