Hi there,
I use the latest gatling version 3.4.0.
I got a soap request to test , and it requires few headers to be added .
I dont see any issues in adding other headers.
However, below error is displayed , when I try to add the header " Referer : SOAPTEST ",
and unable to run the script.
[ERROR] i.g.h.a.HttpRequestAction - ‘httprequest-1’ failed to execute: Failed to build request : j.l.IllegalArgumentException: value could not be parsed into a proper uri, missing scheme
Note: Exact same request with this header returns success response in the postman & Jmeter.
Could not find anything relevant to this in the documentation.
Appreciate your response ,as we are struggling with this issue since last few days , thanks.
Regards
Lenin
I can’t reproduce and doubt this is related to the Referer header. I don’t recall us parsing it.
As required in the group terms:
Provide a Short, Self Contained, Correct (Compilable), Example (see http://sscce.org/)
sorry for that.
Below is the example ( made use of the sample script, comes along with installation ) .However,my actual test script looks similar, wherein I need to set the ‘Referer’ header for a SOAP web service using POST method .
When i try to run the below code snippet , i observe the below error ,
Note: This error does not happen when i use the GET method, instead of POST .
[ERROR] i.g.h.a.HttpRequestAction - ‘httprequest-1’ failed to execute: Failed to build request : j.l.IllegalArgumentException: value could not be parsed into a proper uri, missing scheme
thanks a ton for the quick fix.
So if I try to download Gatling from the below link , will that have the fix for this issue ?
https://repo1.maven.org/maven2/io/gatling/highcharts/gatling-charts-highcharts-bundle/3.4.0/gatling-charts-highcharts-bundle-3.4.0-bundle.zip
sorry, i never tried this before.
Just tried downloading the latest from the below link, and observe the issue still.
https://repo1.maven.org/maven2/io/gatling/highcharts/gatling-charts-highcharts-bundle/3.4.0/gatling-charts-highcharts-bundle-3.4.0-bundle.zip
please let me know how to get the latest bundle with the fix .
As flagged on the Github ticket, this fix will be shipped in the next fix release: 3.4.1.
Thanks for that.Appreciate your support here.
Can you please advise if there is any work around to handle this issue with 3.4.0 ?
As we plan few performance testing deliverables using Gatling over next few weeks for our next project release , looking for some alternate options in gatling to handle this, if any… if not, planning to manage our current release with some other tools ,until we get the fix available for us to use.