diff --git a/files/en-us/web/http/basics_of_http/data_uris/index.html b/files/en-us/web/http/basics_of_http/data_uris/index.html index 935cd7a20c58a9c..c185749e3a4fbda 100644 --- a/files/en-us/web/http/basics_of_http/data_uris/index.html +++ b/files/en-us/web/http/basics_of_http/data_uris/index.html @@ -25,13 +25,15 @@
The mediatype
is a MIME type string, such as 'image/jpeg'
for a JPEG image file. If omitted, defaults to text/plain;charset=US-ASCII
If the data is textual, you can embed the text (using the appropriate entities or escapes based on the enclosing document's type). Otherwise, you can specify base64
to embed base64-encoded binary data. You can find more info on MIME types here and here.
If the data contains characters defined in RFC 3986 as reserved characters, or contains space characters, newline characters, or other non-printing characters, those characters must be percent-encoded (aka “URL-encoded”).
+ +If the data is textual, you can embed the text (using the appropriate entities or escapes based on the enclosing document's type). Otherwise, you can specify base64
to embed base64-encoded binary data. You can find more info on MIME types here and here.
A few examples:
data:,Hello%2C%20World!
Hello, World!
. Note how the comma is percent-encoded as %2C
, and the space character as %20
.data:text/plain;base64,SGVsbG8sIFdvcmxkIQ==
data:text/html,%3Ch1%3EHello%2C%20World!%3C%2Fh1%3E
The Web APIs have native methods to encode or decode to base64: Base64 encoding and decoding.
+The Web APIs have native methods to encode or decode to base64: Base64 encoding and decoding.
url()
url()