URL encoder / URL decoder
As simple as this URL encoder / URL decoder is, as valuable for the daily trafficking of an AdOps, digital campaign manager or SEM and RTB trader.
For example, for an advertising creative or line item, a landing page URL must be appended as a redirect to a click-through URL of an ad server or DSP. Now this landing page has spaces or special characters or parameter passes in the URI string - these are not UTF-8 compliant and a browser would misinterpret them or simply truncate the URI / URL at the first occurrence. That's why you have to encode something like this URI.
On the other hand, you might also want to decode a URL from a link to be able to read it as a human being.
Simple task, yes! But do it by hand. Well, now you have here a URL decoder and URL encoder.
Type your URL string or parts you want to encode into the decoded box and press on URL encode, or vice versa to decode.
If you need your URL to comply with RFC2396 (e.g. a space should be displayed as '+' instead of %20) then check the checkbox.<
If you like it, please buy me a beer -> here
When data is entered in HTML forms, the form field names and values are encrypted and sent to the server in an HTTP request message using the GET or POST method or historically by e-mail. The default encoding is based on a very early version of the general URI percentage encoding rules, with a number of modifications such as newline normalization and replacing spaces with "+" instead of"%20". The MIME type of the data encoded in this way is application/x-wwww-form-urlencoded and is currently (still very obsolete) defined in the HTML and XForms specifications. In addition, the CGI specification contains rules on how web servers decode such data and make it available to applications.
The term URL coding is somewhat imprecise, since the coding method is not limited to URLs (Uniform Resource Locators), but can also be applied to any other URIs (Uniform Resource Identifiers) such as URNs (Uniform Resource Names). Therefore, the term percentage coding should be preferred, URI coding is also common.
The characters allowed in a URI are either reserved or unreserved (or a percent sign as part of a percent encoding). Reserved characters are the characters that sometimes have a special meaning. For example, slashes are used to separate different parts of a URL (or more generally a URI). Unreserved characters have no such meaning. In percentage coding, reserved characters are represented by special character strings. The number of reserved and unreserved characters and the circumstances in which certain reserved characters have a special meaning have changed slightly with each revision of the specifications governing URIs and URI schemes.