온라인 URL 디코더

Consider the following line of code:

string _decoded = System.Web.HttpUtility.UrlDecode(  "There%20should%20be%20text%20after%20this%0022help!");

The encoded line

"There%20should%20be%20text%20after%20this%0022help!" 

when decoded via the website urldecoder.org produces

"There should be text after this22help!"

however the value of _decoded as displayed in the debugger is:Figure 1: Debugger view of problem

What could be causing this problem? Is there a setting or special encoding that will circumvent this in all cases?

EDIT: Yes, I consider this behavior to be an error. I don't want URLDecode to introduce the \0 char to the resultant string, because it would result in an invalid file name (my code is moving around files).

I have a web api that uses .Net 4.7.1 and I noticed some strange behavior when performing a get on one of the endpoints. When I perform a get to the endpoint http://localhost:52684/api/v1/some-resource?client_timezone=%2B0500 the parameter client timezone is received as " 0500" rather than "+0500". the only thing I can think of is that the Url is being decoded twice so the "%2B" turns into "+" and then " ". Does anyone know of any common causes of this or why it might be happening?

Here's a similar endpoint on the controller

[HttpGet][Authorize][ApiRoute("some-resource", StartingVersion = 1)][EnableCors("*", "*", "GET", "*")]public IHttpActionResult SomeResource([FromUri] string timezone){    if (!DataValidationUtililties.IsValidClientTimezone(timezone))    {        return BadRequest();    }    return Ok();}

What's the best JavaScript URL decode utility? Encoding would be nice too and working well with jQuery is an added bonus.

I have array like this

{search: "job", keywords: "", cat: [12,28,38]}

and I need url string like this

?search=job&keywords=&cat%5B%5D=12&cat%5B%5D=28&cat%5B%5D=38

for my query in worpdress

please, help

This code

var serialize = function(obj, prefix) {    var str = [],        p;    for (p in obj) {        if (obj.hasOwnProperty(p)) {            var k = prefix ? prefix + "[" + p + "]" : p,                v = obj[p];            str.push((v !== null && typeof v === "object") ?                serialize(v, k) :                encodeURIComponent(k) + "=" + encodeURIComponent(v));        }    }    return str.join("&");};

and I have this

search=job&keywords=&cat%5B0%5D=12&cat%5B1%5D=28&cat%5B2%5D=38 

but I do not need an index whith "cat"

Currently incorporating the URLEncoder and URLDecoder into some code. There are numerous URLs already saved that will get processed by the URLDecoder routine that was not initially processed by the URLEncoder routine.

Based on some testing it doesn't appear there will be an issue, but granted I have not tested all the scenarios.

I did notice some characters like the / which would normally get encoded are processed just find by the decoding routine even if not initially encoded.

This lead me to an oversimplified analysis. It appears the URLDecoder routine essentially checks the URL for a % and the next 2 bytes (provided UTF-8 is used). As long as there aren't any % within the previously saved off URLs then there shouldn't be an issue when processed by the URLDecoder routine. Does that sound about right?