meow Comments - Answer Overflow

Topics

meow

Explore posts from servers

RReactiflux CDCloudflare Developers DDeno SSolidJS TtRPC TTCTheo's Typesafe Cult HHono DTDrizzle Team

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

I see, I just need to modify my headers then

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

Oh your way works

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

That's from the docs for the rest api

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

No, it looks like

curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID_HERE/d1/database \
    -H "X-Auth-Email: $EMAIL_HERE" \
    -H "X-Auth-Key: $TOKEN_HERE"

curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID_HERE/d1/database \
    -H "X-Auth-Email: $EMAIL_HERE" \
    -H "X-Auth-Key: $TOKEN_HERE"

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

my global key gets through on curl

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

I'll see if I get the same error with curl & my global key as well

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

I get the same error with curl

12 replies

CDCloudflare Developers

•Created by Max (@rozenmd) on 2/6/2025 in #d1-database

Minimum D1 permissions for HTTP API

I tried and same auth error

12 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

They specifically ban blank objects, I see

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

Ah hmm

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

And when I inspect the response on the other end it returns an object on the other end since that's valid JSON

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

But the above route truly does return never

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

Your advice works and I'm gonna be doing that

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

I simplified it to just this

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

  .get("/", async (c) => {
    return c.json({})
  })

  .get("/", async (c) => {
    return c.json({})
  })

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

Try it directly. Create an empty route that just does return c.json({})

69 replies

•Created by meow on 1/25/2025 in #help

No Types for RPC with abstracted routes

It should just be an empty object!

69 replies