Forum Discussion
The header option is at the bottom
I thought header can be modified
- Bill_In_Irvine8 years agoContributor
I tried the Headers at the top and haven't tried the headers tab at the bottom until just now. but I get the same error. It's as though the parameter part is still not seen. The raw request looks good and the only difference is the user agent is Apache-HttpClient/4.5.2 with Ready API.
I notice that for PUT or POST, under the Projects tab you can check "POST QueryString" to send parameters in with the message body. That seems to be what Curl is doing. But Ready! API disallows this.
- Bill_In_Irvine8 years agoContributor
Just an update. I have been doing lots of researching on this and tried even using Groovy scripting in a requestFilter event handler to set the message body and try to trick the SoapUI NG to duplicate the curl command. The --data or -d in curl, according to the documentation, is like a POST:
" -d:
(HTTP) Sends the specified data in a POST request to the HTTP server, in the same way that a browser does when a user has filled in an HTML form and presses the submit button. This will cause curl to pass the data to the server using the content-type application/x-www-form-urlencoded."
However when using a curl -X GET -k ... command and -d in combination, curl somehow converts it back to a GET request. I tried using wireshark to see exactly what is going on but our key exchange agreement is DH-based, so I cannot decrypt the packets.
I am at a loss at how something so basic like this has not been addressed.