Response improvements

[ebidel]

For further parity with https://developer.mozilla.org/en-US/docs/Web/API/Response, these would be useful to add

• Response.statusText
• Response.redirected
• Request.type

[aslushnikov]

We gave up on aligning with fetch api: #106

So we'd rather not add anything to the api unless there's a real-world user scenario to prove the necessity.

[ebidel]

I filed this because I ended up wanting all 3 when trying out network interception apis for the first time. If I ran into it in < 5min I suspect others will want it to.

use cases:

• Response.type in particular is pretty handy to know the initiator of a request (xhr, script, parser).
• statusText is useful b/c people parse out custom messages from server responses. -
• Response.redirected is just nice to know.

[ebidel]

BTW, we should try to keep features requests open so people can find and subscribe to them more easily. Also helps us prioritize!

[aslushnikov]

Response.type in particular is pretty handy to know the initiator of a request (xhr, script, parser).

That's not what response.type is: https://developer.mozilla.org/en-US/docs/Web/API/Response/type
Do you mean request.type?

The response.redirected is easy to polyfill:

let redirected = 300 <= response.statusCode && response.statusCode <= 399;

statusText is useful b/c people parse out custom messages from server responses.

Ahh, I see. We should plumb this from interception then.

BTW, we should try to keep features requests open so people can find and subscribe to them more easily. Also helps us prioritize!

That's right, however we don't want to be buried under the unmanageable pile of issues. For this reason we aggressively close everything we don't feel like implementing. It's totally fine to comment or reopen to argue :)

[ebidel]

Yep, request.type.

[itaysabato]

statusText seems like a very basic (and easy) thing to expose. And I need it :)

[aslushnikov]

@itaysabato we don't have status text for the intercepted requests; however, we'll get it for free once a huge on-going refactoring of network layer in chromium completes. No good ETA on this though.