Re: [whatwg/fetch] Add usage advice for Sec- (PR #1818)

johannhof left a comment (whatwg/fetch#1818)

Martin, thanks for writing this up - Another reason that we liked using Sec- for Storage-Access Headers was that the Sec- namespace is automatically reserved by virtue of the entire prefix being forbidden, making conflicts with existing custom application headers impossible.

Do you have any thoughts on that and should we consider this in advice we give to browser developers?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1818#issuecomment-2767365707
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1818/c2767365707@github.com>