Bilal Mahmoud

O yea sorry! I was kind of in a hurry when creating the issue 😅, so I wasn't really able to create a repro repo. Sorry! I'll update the issue...

I have created a minimal reproductive repository using SolidStart and have linked it to the issue description. Sorry again, and I hope this helps!

Thanks for the info. I'll try that tomorrow. I just had a look over the source code, and I think I figured out what was happening: warp-reverse-proxy is initiated here:...

I have been doing some experimentation (HTTPS proxies are kind of a new thing to me^^), and supporting HTTPS is a bit more involved due to the use of `CONNECT`....

I found kind of a workaround, which forces HTTP: deploy mitmproxy: `mitmweb --mode reverse:` and then change the domain I am trying to connect to to the proxy-server URL. This...

Yes, kind of. I would need to implement `Record` for the non-blocking variant. The problem here is twofold: the request and response are evaluated eagerly (from my just look over...

This also fixes another bug that was present (unintentionally?) where the code would correctly detect the worker scope but then refer to the globals instead of the worker scope.

Shiming with `isomorphic-ws` I get `panicked at [...]/libp2p-websocket-websys-0.3.1/src/lib.rs:308:14: to have a window or worker context`

I continued digging and found that the "polyfill" worked. This is no real solution, but it seems not as hard to support as expected. ```ts // @ts-ignore global.WebSocket = require('isomorphic-ws');...

In multi-context environments, packages usually use [`isomorphic-ws`](https://www.npmjs.com/package/isomorphic-ws). I have no problem adding that to the global scope, but the other hacks to make `WebContext` work worry me, as these changes...