I created an OPTIONS HTTP request and add few parameters. All parameters were not passed to the server.
Hello, Could you show how you configure your Sampler ? Thanks
It looks like the samplers don't expect to send parameters for an OPTIONS method. Were you expecting the parameters to be sent as part of the OPTIONS line, or as a part of a content body? JMeter does support sending parameters as part of the OPTIONS line; you just have to include them as part of the path, rather than as parameters in the table below.
(In reply to Sebb from comment #2) > JMeter does support sending parameters as part of the OPTIONS line; you just > have to include them as part of the path, rather than as parameters in the > table below. I meant to say that this is a bug in JMeter.
If I created OPTION HTTP Request with parameters described in parameters table the request is not passed them down. If I change method to GET I will able to see all parameters as a part of GET request: GET .../?param1=value1
(In reply to Kiryl Halinouski from comment #4) > If I created OPTION HTTP Request with parameters described in parameters > table the request is not passed them down. If I change method to GET I will > able to see all parameters as a part of GET request: GET .../?param1=value1 Yes, already noted. And the workround is to use the Path field, for example http://host/path?p1=v1 However the question I asked was about how you expected the parameters to be sent to the server. Did you expect them to be passed as part of the URL, or as part of a content body?
(In reply to Sebb from comment #5) > (In reply to Kiryl Halinouski from comment #4) > > If I created OPTION HTTP Request with parameters described in parameters > > table the request is not passed them down. If I change method to GET I will > > able to see all parameters as a part of GET request: GET .../?param1=value1 > > Yes, already noted. > And the workround is to use the Path field, for example > > http://host/path?p1=v1 > > > However the question I asked was about how you expected the parameters to be > sent to the server. > > Did you expect them to be passed as part of the URL, or as part of a content > body? I think that it should work the same way as a GET request where it converts automatically parameters from the table to pairs key=value and ad them to the URL as you shown before. I think that is the right way how it should be implemented for OPTION request. Otherwise< the parameters table does not have any sense for me.
Author: pmouawad Date: Sat Feb 25 14:43:32 2017 New Revision: 1784383 URL: http://svn.apache.org/viewvc?rev=1784383&view=rev Log: Bug 56939 - Parameters are not passed with OPTIONS HTTP Request Bugzilla Id: 56939 Modified: jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPSamplerBase.java jmeter/trunk/xdocs/changes.xml
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3427