Re^2: Technobabble (was: Re: Adding recognition of Gemini to URI.pm?)

Gotta wonder about their (or my) technical competency.

Response headers MUST be UTF-8 encoded text and MUST NOT begin with the Byte Order Mark U+FEFF.

Considering U+FEFF is the UTF-16 BOM, not the UTF-8 BOM, I don't know why it ever would. lol

Update: Well, wee-pee says "If the Unicode byte-order mark U+FEFF is at the start of a UTF-8 file, the first three bytes will be 0xEF, 0xBB, 0xBF" ... which doesn't quite make sense to me. "If it starts with A, it starts with B." Hmm...

Comment on Re^2: Technobabble (was: Re: Adding recognition of Gemini to URI.pm?)

Replies are listed 'Best First'.
Re^3: Technobabble (was: Re: Adding recognition of Gemini to URI.pm?) by ikegami (Patriarch) on Oct 12, 2024 at 15:15 UTC
Considering U+FEFF is the UTF-16 BOM, not the UTF-8 BOM Not so. U+FEFF is also the BOM "for UTF-8". It's simply the BOM, period.^[1] In UTF-16be streams, it's encoded as `FE FF`. In UTF-16le streams, it's encoded as `FF FE`. In UTF-8 streams, it's encoded as `EF BB BF`. These are (some of) the byte sequences looked for, but they're all (encodings of) U+FEFF. It's also the ZWNBSP if found somewhere other than the start of a stream, but that use has been deprecated in favour of U+2060 WORD JOINER.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Technobabble (was: Re: Adding recognition of Gemini to URI.pm?)
by ikegami (Patriarch) on Oct 12, 2024 at 15:15 UTC

Considering U+FEFF is the UTF-16 BOM, not the UTF-8 BOM

Not so. U+FEFF is also the BOM "for UTF-8". It's simply the BOM, period.^[1]

In UTF-16be streams, it's encoded as FE FF.
In UTF-16le streams, it's encoded as FF FE.
In UTF-8 streams, it's encoded as EF BB BF.

These are (some of) the byte sequences looked for, but they're all (encodings of) U+FEFF.

It's also the ZWNBSP if found somewhere other than the start of a stream, but that use has been deprecated in favour of U+2060 WORD JOINER.

[reply]
[d/l]
[select]