Encoder Url Online

I would like to make cURL/Elasticsearch understand HTTP query parameters passed as normal strings while being url encoded by the command.

If I run this HTTP GET via cURL to submit the query to Elasticsearch:

curl \  -H 'Content-Type: application/json' \  -XGET '127.0.0.1:9200/movies/movie/_search?q=%2Byear%3A%3E1980+%2Btitle%3Astar%20wars&pretty'

Then I am able to retrieve the expected documents.

However if I run this cURL query:

curl \   -H 'Content-Type: application/json' \   --data-urlencode "pretty" \   --data-urlencode "q=+year:>1980 +title:star wars&pretty" \   -XGET '127.0.0.1:9200/movies/movie/_search'

Then I get this error:

{    "error": {        "root_cause": [{            "type": "json_parse_exception",            "reason": "Unrecognized token 'pretty': was expecting ('true', 'false' or 'null')\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@7856627; line: 1, column: 8]"        }],        "type": "json_parse_exception",        "reason": "Unrecognized token 'pretty': was expecting ('true', 'false' or 'null')\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@7856627; line: 1, column: 8]"    },    "status": 500}

I am using:

• cURL version 7.47.0 which should understand the command parameter --data-urlencode
• Elasticsearch 6.3.1

My script searches a website for songs, but when there are spaces it doesn't search, you have to add underscores. I was wondering if there was a way to replace my spaces with underscores.Could you please use my current code below to show me how to do it?

set search to text returned of (display dialog "Enter song you wish to find" default answer "" buttons {"Search", "Cancel"} default button 1)open location "http://www.mp3juices.com/search/" & searchend

I am passing my variables as follows to url using GET method

http://www.mysite.com/demo.php?sid=123121&email_id=stevemartin144%40gmail.com

& when i print $_GET on demo.php it displays parameters as follows:

email_id    stevemartin144@gmail.comsid 123121

instead of above output i want parameters as i passed

email_id    stevemartin144%40gmail.comsid 123121

I don't want to convert %40 into @

please suggest me solution on this

Thanks in advance

I am trying this API from "YOURS" where if the lat and lng are positive values, everything is working fine but if any of them is negative it is failing.

Here is the failing request request: http://www.yournavigation.org/api/1.0/gosmore.php?format=kml&flat=38.8999732&flon=-77.030323&tlat=38.8988335&tlon=-77.0349257&v=motorcar&fast=1&layer=mapnik

Here is the working request: http://www.yournavigation.org/api/1.0/gosmore.php?format=kml&flat=30.633793&flon=76.828155&tlat=30.620916145882216&tlon=76.82464767254594&v=motorcar&fast=1&layer=mapnik

I am trying to do this from an iOS device. I don't think I need to URL encode "-"?

The most recent documentation for urllib states:

Changed in version 3.7: Moved from RFC 2396 to RFC 3986 for quoting URL strings. “~” is now included in the set of reserved characters.

Why is this the case? In RFC 3986, ~ is not a reserved character:

 reserved    = gen-delims / sub-delims gen-delims  = ":" / "/" / "?" / "#" / "[" / "]" / "@" sub-delims  = "!" / "$" / "&" / "'" / "(" / ")"             / "*" / "+" / "," / ";" / "="

Explicitly in the next section it is included as an unreserved character:

2.3. Unreserved Characters

Characters that are allowed in a URI but do not have a reserved purpose are called unreserved. These include uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde.

 unreserved  = ALPHA / DIGIT / "-" / "." / "_" / "~"

Furthermore, later on, the RFC states that (emphasis mine):

For example, the octet corresponding to the tilde ("~") character is often encoded as "%7E" by older URI processing implementations;

So it seems like 3.7 is inconsistent: it asserts the support for the newer RFC while simultaneously regressing the processing of ~. (In fact, in the older RFC, ~ is also not reserved nor 'unwise')