Allow fetch unstable APIs in Deno to query a TLS certificate-protected server

[tgdn]

Is your feature request related to a problem? Please describe.
I'd like to use the fetch unstable API from Deno in order to use a client certificate to make requests to a secured server.

Describe the solution you'd like
Allow basic unstable APIs from Deno. Right now Deno on supabase is very limited, it's impossible to use for even simple use cases such as this one.

Describe alternatives you've considered
Either there is a solution or I'll have to use something other than supabase.

I've tried using Deno.createHttpClient, but it's undefined once deployed on supabase.

Thanks!

[vincaslt]

It's important to me as well. I need to be able to create proxies via Deno.createHttpClient(). I've registered an issue on edge-runtime repository: #205

[sweatybridge]

Transferring to edge runtime repo because it likely requires changes to the container.

[predragcvetkovski]

Hey @sweatybridge can we get an update on the resolution of this issue? If resolved, can we get some documentation on how to make it work? Without this feature, we must switch to AWS Lambda and use NodeJS.

[wouterpeere]

Any news related to this issue? I ran into it today ...

[smndtrl]

Hej @nyannyacha, while continuing to try out develop I came across this case. Is this something that can be addressed now that it is standard and stable in deno?

[nyannyacha]

@smndtrl Yeah, API has been stabilized in Deno 2.x.

develop branch tracks Deno 2.1.4, so the API should be available.
This issue will be closed when develop is merged into main.

[smndtrl]

Thanks for clarifying @nyannyacha. The API isn't currently in develop. It is part of ext/fetch (https://github.com/denoland/deno/blob/v2.1.4/ext/fetch/22_http_client.js) of deno and edge runtime only has a small selection of upstream ext/.
Is this sth your still planning to include before develop gets merged?

[nyannyacha]

For deno_fetch, it doesn't exist in the ext because there is nothing to modify separately for the edge runtime, it is being pulled as a direct dependency (see Cargo.toml in the root).

Did it not work in the develop branch? I'll check it out soon, this is a stabilized API so we should support it too.

[smndtrl]

@nyannyacha I get [Error] TypeError: Deno.createHttpClient is not a function insupabase-edge-runtime-1.68.0-develop.8.

Code is very simple

    const httpOptions: Deno.CreateHttpClientOptions  = {

    }

    const tlsOptions: Deno.TlsCertifiedKeyPem  = {
      key: "...",
      cert: "..."
    }

    const client = Deno.createHttpClient({...httpOptions, ...tlsOptions})

[nyannyacha]

Hello @smndtrl 😁

This appears to be simply not exposing that API from the edge runtime. A patch will be submitted soon.
Thanks for letting me know!

[github-actions]

🎉 This issue has been resolved in version 1.68.0-develop.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀