lambdaisland.uri.normalize — lambdaisland/uri 1.3.45

char-seq clj/s

(char-seq str)

(char-seq str offset)

Return a seq of the characters in a string, making sure not to split up UCS-2 (or is it UTF-16?) surrogate pairs. Because JavaScript. And Java.

character-classes clj/s

Which characters should be percent-encoded depends on which section of the URI is being normalized. This map contains regexes that for each case match the characters that need encoding.

hex-code-point? clj/s

(hex-code-point? cp)

normalize clj/s

(normalize uri)

Normalize a lambdaisland.uri.URI.

normalize-path clj/s

(normalize-path path)

normalize-query clj/s

(normalize-query s)

Normalize the query section of a URI

• sub-delimiters that are not percent encoded are left unencoded
• sub-delimiters and other reserved characters are always percent encoded
• non-reserved characters that are percent-encoded are decoded

percent-decode clj/s

(percent-decode s)

The inverse of percent-encode, convert any %XX sequences in a string to characters. Byte sequences are interpreted as UTF-8. To use a different encoding. re-bind *character-encoding*

percent-encode clj/s

(percent-encode component)

(percent-encode component type)

Convert characters in their percent encoded form. e.g. (percent_encode "a") #_=> "%61". When given a second argument, then only characters of the given character class are encoded, see character-class.

Characters are encoded as UTF-8. To use a different encoding. re-bind *character-encoding*

sub-delims clj/s

RFC3986 section 2.2

The purpose of reserved characters is to provide a set of delimiting characters that are distinguishable from other data within a URI. URIs that differ in the replacement of a reserved character with its corresponding percent-encoded octet are not equivalent. Percent- encoding a reserved character, or decoding a percent-encoded octet that corresponds to a reserved character, will change how the URI is interpreted by most applications. Thus, characters in the reserved set are protected from normalization and are therefore safe to be used by scheme-specific and producer-specific algorithms for delimiting data subcomponents within a URI.