Re: [whatwg/fetch] Define ABNF for `origin-or-null. (PR #1924)

mikewest left a comment (whatwg/fetch#1924)

I think it makes a good deal of sense to avoid depending upon Origin and URI. I think we'd just end up copying things for the most part, though: we'd want to define `scheme` (which I think we'd just copy), `port` (which we'd also just copy, though maybe with a length limit?), and `host` (which is complicated, pulling in the IP-related syntaxes, etc).

I'm not sure we'd actually diverge from the RFC on any of those but `host`. There I think we'd copy the IP bits and shift from `reg-name` to a subset of `unreserved` that covered punycode (`ALPHA *( ALPHA / DIGIT / "-" / "." )`, if we didn't want to get too specific).

Is that more or less what you're thinking? If so, I can look at the grammar more deeply tomorrow to figure out how it lines up with our origin serialization algorithms.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1924?email_source=notifications&email_token=ACLYVMJ3CDQXRHZL5AB4SJT4W6MOFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRZGAYDKNZTHE2KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4290057394
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1924/c4290057394@github.com>