https://issues.apache.org/bugzilla/show_bug.cgi?id=56939
--- Comment #6 from Kiryl Halinouski <[email protected]> --- (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.
