Bug 56939 - Parameters are not passed with OPTIONS HTTP Request
Summary: Parameters are not passed with OPTIONS HTTP Request
Status: RESOLVED FIXED
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 2.11
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 07:45 UTC by Kiryl Halinouski
Modified: 2017-02-25 14:43 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kiryl Halinouski 2014-09-10 07:45:54 UTC 
I created an OPTIONS HTTP request and add few parameters. All parameters were not passed to the server.
Comment 1 Philippe Mouawad 2014-09-12 21:01:52 UTC 
Hello,
Could you show how you configure your Sampler ?
Thanks
Comment 2 Sebb 2014-09-12 22:02:06 UTC 
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.
Comment 3 Sebb 2014-09-12 22:12:08 UTC 
(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.
Comment 4 Kiryl Halinouski 2014-09-15 09:11:19 UTC 
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
Comment 5 Sebb 2014-09-15 16:08:31 UTC 
(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?
Comment 6 Kiryl Halinouski 2014-09-15 17:09:51 UTC 
(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.
Comment 7 Philippe Mouawad 2017-02-25 14:43:55 UTC 
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