Encoder Url ออนไลน์

I'm using PlaceAutocomplete to get a place name, which I then url encode and send to a remote host as part of a GET request (in the URL).

At the remote host, I'm finding that some user devices are sending single quotes that are escaped, which is causing a problem because the place name is sent as part of the URL.

e.g. "Andy's Place" is being sent as "Andy\'s Place"

and the backslash \ is a problem when part of a URL for obvious reasons.

... but mostly, this doesn't happen... e.g. on my own test devices it doesn't... the place is sent/received as "Andy's Place".

I'm trying to go through the chain from start to finish to see where the unintended escaping might be happening. I've tried to summarise the chain below, leaving out some stuff along the way (e.g. I don't only send the placeName, I send it with other stuff too)... I hope I've included all important bits:

Place place = PlaceAutocomplete.getPlace(this, data);String placeName = (String) place.getName();EditText_placeName.setText(placeName);// ... later ...String newPlaceName = EditText_placeName.getText().toString();String encodedPlaceName = Uri.encode(newPlaceName);URL url = new URL(strBaseURL + '/' + encodedPlaceName);HttpURLConnection connection = (HttpURLConnection) url.openConnection();responseCode = connection.getResponseCode();

Is there anything in the above chain that could introduce an unwanted escape character in the URL on some devices but not others?

As a sort of footnote, I know that sending the data by POST (in the body) rather than GET (as part of the URL) is likely to be better (will probably solve my problem completely), and indeed this is what I'm now moving towards, but I'd still like to know how that \ character is getting through the above chain, at least partly out of curiosity.

I am new to AngularJS, so forgive me if this is obvious, but I am looking for someone who can answer this tricky question. I am implementing an application, and need to pass some parameters to a particular view to display details about a book. Basically I would like to be able to use the following routing expressions:

bookApp.config(['$routeProvider', function($routeProvider) {    $routeProvider.        when('/catalog', {            templateUrl: 'cataloglist.htm',            controller: 'catCtrl'        }).        when('/book/:title/:chapter', {            template: 'chapterdetail.htm',            controller: 'chapterCtrl'        }).        otherwise({            template: 'oops ... do not understand that route',        });    }]);

The expression /book/:title/:chapter should allow me to pass in the name of the title of a book. I am expecting to be able to pass ANY title of any book in there. To make sure that things are properly delimited, I am going to URL encode the title value, so that in the encoded value there will be no slashes and the value will be clearly delimited by the slash characters. This is the normal way to construct URLs that contain values.

The problem is that there exist book titles that contain the slash character (e.g. The 3/5 solution) This is URL encoded as The+3%2F5+Solution. So can construct a URL like this:

 /app/#/book/The+3%2F5+Solution/The%20Beginning

However, my experience seems to show that the entire value is URL decoded BEFORE it is broken into parameters! This means that any data value with a slash in it, will be misinterpreted as two values, and the pattern matching of the route parameters is broken, and only the first half of the value is passed in. Furthermore, the chapter might have a slash in the name as well.

If I was making a REST service, I would URL encode the value, and the URL will be parsed into pieces BEFORE each piece is decoded. For example, I can use query parameters in a URL like this:

app.jsp?title=The+3%2F5+Solution&chapter=The%20Beginning

and this will work correctly. Using URL encoding, I can pass ANY string value in the title. I would have expected route parameters to do the same thing ... but I already mentioned I am NEW to AngularJS.

To decode the %2F into a slash BEFORE determining the pieces seems like a very serious bug. Apparently, you simply can't pass values with a slash in them as route parameters. Am I missing something here? What is the solution to allow me to safely pass a book name with ANY possible character in it (along with a chapter title with ANY character in it), as a route parameter?

I'm using NSURLComponents and I can't seem to get the query values to encode correctly. I need the final URL to represent a + as %2B.

let baseUrl = NSURL(string: "http://www.example.com")    let components = NSURLComponents(URL: baseUrl, resolvingAgainstBaseURL: true)components.queryItems = [ NSURLQueryItem(name: "name", value: "abc+def") ]XCTAssertEqual(components!.string!, "http://www.example.com?connectionToken=abc%2Bdef")

Failed!

Output equals:

http://www.example.com?connectionToken=abc+def 

NOT

http://www.example.com?connectionToken=abc%2Bdef

I've tried several variations and I just can't seem to get it to output %2B at all.

is there any js function to convert an array to urlencoded? i'm totally newbie n JS... thanks!...

my array is a key & value array....so,

myData=new Array('id'=>'354313','fname'=>'Henry','lname'=>'Ford');

is the same as

myData['id']='354313';myData['fname']='Henry';myData['lname']='Ford';myData.join('&'); //returns error, it doesn't work on such array...

is there any solution?

oh sory...i have an array like this

var myData=new Array('id'=>'354313','fname'=>'Henry','lname'=>'Ford');

then i need the array converted to be:

id=354313&fname=Henry&lname=Ford

Is there a difference between Server.UrlEncode and HttpUtility.UrlEncode?