Michael Solomon
Michael Solomon
This behavior looks correct; I'm not sure the code does it. From what I see: ```js compressResponse(['gzip', 'br'])('hello world').toString('base64')); // H4sIAAAAAAAAA+NmbchIzcnJVyjPL8pJYQYAhavvgA8AAAA= ``` Produce a string that is br -> gzip,...
IIRC, `Content-Encoding` header is "in the order they were applied", so the string is first compressed to gzip, and only then compressed to br, so the decompression should go backward....
> Your example is incorrect. Why not? If I compressed by `gzip, br`, I expect to decompress by be -> gzip. Isn't it?
Opened a PR in `interceptors` repo
I'm not familiar with this package, but we do manage the custom agent. The issue with the `rejectUnauthorized` option in your example repo is that it relates to the agent's...
I see. [This](https://github.com/mswjs/interceptors/pull/701) has resolved only the `options` forwarding issue. The `HttpsProxyAgent` pertains to a different problem. You can find more information [here](https://github.com/mswjs/interceptors/issues/675#issuecomment-2537406917).
I think it's fixed. Please test: `npm i nock@latest`
@sebws do you mean something like: ```js public createConnection(options: any, callback: any) { const createConnection = this.customAgent.createConnection || super.createConnection ```
I think we should let users use whatever agent they want: ```diff public createConnection(options: any, callback: any): net.Socket { - const createConnection = - this.customAgent instanceof https.Agent - ? this.customAgent.createConnection...
> is there a reason it's not as simple as doing the instanceof check in the .bind call as well? Could you provide a code example to clarify your point?