The safest “correct” method would be: Parse the url into an array with parse_url() Extract the query portion, decompose that into an array using parse_str() Delete the query parameters you want by unset() them from the array Rebuild the original url using http_build_query() Quick and dirty is to use a string search/replace and/or regex to … Read more
Use URLDecoder.decode(proxyRequestParam.replace(“+”, “%2B”), “UTF-8”) .replace(“%2B”, “+”) to simulate decodeURIComponent. Java’s URLDecoder decodes the plus sign to a space, which is not what you want, therefore you need the replace statements. Warning: the .replace(“%2B”, “+”) at the end will corrupt your data if the original (pre-x-www-form-urlencoded) contained that string, as @xehpuk pointed out.
Simple solution You can use URLSearchParams.set() like below: var currentUrl=”http://www.example.com/hello.png?w=100&h=100&bg=white”; var url = new URL(currentUrl); url.searchParams.set(“w”, “200”); // setting your param var newUrl = url.href; console.log(newUrl); Online demo (jsfiddle)
The answer is not simple. The following is extracted from section 3.2.2 of RFC 3986 : A host identified by an Internet Protocol literal address, version 6 [RFC3513] or later, is distinguished by enclosing the IP literal within square brackets (“[” and “]”). This is the only place where square bracket characters are allowed in … Read more
Use a parameter name in the query string. If you have an action: public void DoSomething(string[] values) Then use values in the query string to pass an array to a server: ?values=this&values=that
The differences between Matrix parameters and Query Parameters are much more than just convention. The main differences are: urls with query params won’t have their response cached by intermediaries/proxies (at present) matrix parameters may appear anywhere in path calculating the relative uri is different query params are generally abused to add new verbs instead of … Read more
As a matter of modern spec, yes, it is permissible to skip the slash, contrary to what the accepted answer here claims. Although the accepted answer correctly quotes RFC 1738 (released over 20 years ago!), it wrongly claims that RFC 2396 (released in 1998) requires the slash, and neglects that both of those specs have … Read more
What are the best practices and considerations of choosing between 1 and 2 above? Usually the content body is used for the data that is to be uploaded/downloaded to/from the server and the query parameters are used to specify the exact data requested. For example when you upload a file you specify the name, mime … Read more
Add the following library to your application libraries. It overrides the behaviour of the default Input library of clearing the $_GET array. It allows for a mixture of URI segments and query string. application/libraries/MY_Input.php class MY_Input extends CI_Input { function _sanitize_globals() { $this->allow_get_array = TRUE; parent::_sanitize_globals(); } } Its also necessary to modify some configuration … Read more
React router from v4 onwards no longer gives you the query params in its location object. The reason being There are a number of popular packages that do query string parsing/stringifying slightly differently, and each of these differences might be the “correct” way for some users and “incorrect” for others. If React Router picked the … Read more