Gustaf Räntilä

FYI I just built [awesome-code-frame](https://www.npmjs.com/package/awesome-code-frame) to get rid of e.g. this but also have better support for colors, including in browsers.

Interesting, it _is_ implemented, but perhaps it retries over the same session which is what the server doesn't want. Will look into this.

You can do this per-context using the [`session`](https://github.com/grantila/fetch-h2#low-level-session-configuration) option. So, if you want this globally for your app, before doing any fetch call, set it up using e.g.: ```ts const...

I think it might work over https, but these properties aren't forwarded for plain http now that I look at it. I'll fix this as soon as I'm done with...

Is this on HTTP 2?

> What should happen here? That's the question. Either fail the whole fetch request (I don't think that's right), or ignore _only the invalid_ cookies. Catching the exception is a...

`http` (at least 1) is entirely stateless, and whatever headers is being received is up to the higher layer to deal with, in this case Fetch. I will fix this...

No there's no such support, but it certainly can be implemented if it's useful.

Help on this is welcome, if it's of somewhat importance to anyone. * Can the `originSet` be trusted to use as-is? * Does Node.js filter invalid results? * Does Node.js...

Hmm, what can you do with such a response? Is it at all useful? Surely it's proper HTTP (if the headers and body is well-formed), but semantically it's similar to...