You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2014/09/10 09:45:54 UTC
[Bug 56939] New: Parameters are not passed with OPTIONS HTTP Request
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
Bug ID: 56939
Summary: Parameters are not passed with OPTIONS HTTP Request
Product: JMeter
Version: 2.11
Hardware: PC
OS: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: kirylh@gmail.com
I created an OPTIONS HTTP request and add few parameters. All parameters were
not passed to the server.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |p.mouawad@ubik-ingenierie.c
| |om
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
Could you show how you configure your Sampler ?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
--- Comment #3 from Sebb <se...@apache.org> ---
(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.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
--- Comment #2 from Sebb <se...@apache.org> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #5 from Sebb <se...@apache.org> ---
(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?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
--- Comment #6 from Kiryl Halinouski <ki...@gmail.com> ---
(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.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
Kiryl Halinouski <ki...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56939] Parameters are not passed with OPTIONS HTTP Request
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
Kiryl Halinouski <ki...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #4 from Kiryl Halinouski <ki...@gmail.com> ---
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
--
You are receiving this mail because:
You are the assignee for the bug.