Daniel Lamando

I would've loved for this to be cut-and-dry but another request with a comma in the URL is requiring a single-encode. I'm going to open an AWS ticket about this.

> My issue seem related to initial post as it started at 1.29.3. Have you tried updating your Docker engine? Or are you running Alpine Linux directly on a machine?

For me, the solution was updating my Docker engine. Deno stopped encountering the panic after Docker was upgraded. If possible, I'd recommend checking and updating your Docker engine as well

Hi, I'm also looking for HTTP over Unix. I find the above usage of 'proxy' interesting because the term is already defined for http interactions; case in point, `Deno.createHttpClient({ proxy:...

[I've published a workaround](https://github.com/cloudydeno/deno-socket_fetch) as `/x/socket_fetch` which implements a small subset of HTTP/1.1 in Typescript, so that Deno's support for bare Unix sockets can be used to send basic HTTP...

Hello, this exact problem is probably off-topic for this thread, which is that Deno cannot connect to IP address hosts using HTTPS. --- However, I can confirm that Deno has...

> in the meantime, anyone who runs into this can create an entry in their hosts file as a workaround. Based on this quote and my own use-case for this...

I've been quiet for a year or so :) just checking in. It looks like the error message is different nowadays (Deno 1.29.1) for IPv4: `presented server name type wasn't...

I forgot to mention a workaround: **`Deno.connect` and `Deno.startTls` can be used together** to provide different `hostname` values for the TCP and TLS aspects of a connection, instead of `Deno.connectTls`...

Hello, I haven't actually started editing code on this plugin, as it's kinda more of a 'nice to have' value-add to kong in my situation. I think the main concerns...