Re: [fetch] Stop hardcoding the list of schemes that inherit HTTPS state (#255)

Sure, and those that are standardized/interoperable make it to this list. I guess I could acknowledge that some implementations chose not to follow the specification and that for the schemes for which that is true it's a "chose your own adventure".

Anyway, even if there were more schemes and it was open-ended, each scheme would still be required to have a specification that defines how it creates a response, including HTTPS state, so I'm not sure how to satisfy the request. Unless there's classes of schemes that could have some kind of code reuse perhaps?

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