My curl searches result in "Unparsable URI-encoded request data". Is curl version 7.15.5 unsupported?

[benjaminw]

My curl searches result in the output

Unparsable URI-encoded request data

I see that many of the curl searches on this site include the switch --data-urlencode, but when I include this in my searches, curl replies that the feature is unknown. My curl version is 7.15.5, and the latest version available is 7.49ish. Can anyone confirm that the --data-urlencode feature is necessary to perform some searches, or that my version of curl is outdated for Splunk queries?

Many thanks!

[jkat54 · Accepted solution]

You will not require --data-urlencode if you want to encode your own url manually

for example... equals sign (=) becomes %3d once encoded.

You can use an online encoder like this one instead of --data-urlencode
http://meyerweb.com/eric/tools/dencoder/

When i encode the url of my answer i get:
https%3A%2F%2Fanswers.splunk.com%2Fanswers%2F418333%2Fmy-curl-searches-result-in-unparsable-uri-encoded.html%23answer-418465

So now I could use:

curl -k 'https%3A%2F%2Fanswers.splunk.com%2Fanswers%2F418333%2Fmy-curl-searches-result-in-unparsable-uri-encoded.html%23answer-418465'

[benjaminw]

Jkat54, thank you! This encoding site is exactly what I needed!

[jkat54]

You are very welcome @benjaminw