`[ERROR] A request to the Cloudflare API failed`
[ERROR] A request to the Cloudflare API failed
HYou would paste the ID and Key you got from https://dash.cloudflare.com/?to=/:account/calls
Ahttps://developers.cloudflare.com/calls/example-architecture/
looks like the example image and numbers dont match up
looks like the example image and numbers dont match up
Aand also i believe there is a typo on https://developers.cloudflare.com/calls/https-api/#lifecycle-of-a-simple-session
"Remote Client Joints" instead of "Remote Client Joins"
"Remote Client Joints" instead of "Remote Client Joins"
Cloudflare Docs
Cloudflare Calls simplifies the management of peer connections and media tracks through HTTPS API endpoints. These endpoints allow developers to …
Jwhat doesn't match up? seems fine to me on a quick read
HThe 6 bubble is in Admin, which is list item 4
Jgood catch! You might want to open up a docs PR/issue: https://github.com/cloudflare/cloudflare-docs/blob/production/content/calls/https-api.md
A5 in the image is 6 in the bottom area
admin bubble is 6 when it should be 4
admin bubble is 6 when it should be 4
Jah yeah, also good catch
Ja docs issue would be best for that
Awill do
XIn what text format? I tried only secret value, VALUE=SECRET, etc
XEnter a secret value:
XIt does not accept
XAPI calls fail
Awhen you use
wrangler secret put CALLS_APP_SECRETok. I needed add correct app ID, account ID etc, then it did work.
.Trying to understand something with workers, if I am gonna rate limit my api, would it not be better to do this in a worker so it doesn’t hit my origin server at all?
.Is there any good rate limit packages that work with itty router ?
JI'm not sure about packages, but you might be interested in the new rate limiter bindings announced during dev week: https://blog.cloudflare.com/workers-production-safety#new-rate-limiting-api-in-workers
Wthe type is based on the extension of the path
WSince it's at request time that it's categorised
WThe network tab shows requests and their responses, the category it puts it in is based on the request path (e.g.
Things don't show up after a response, it's on request so there's no content-type available to use
//abc.jsThings don't show up after a response, it's on request so there's no content-type available to use
SDoes returning response with status code 500 automatically send this page?
I can not tthink of anything else that could do this, the docs say its from a javascript exception but locally it runs fine no exceptions
I can not tthink of anything else that could do this, the docs say its from a javascript exception but locally it runs fine no exceptions
KDoes returning response with status code 500 automatically send this page?Nope
Wno there's an exception happening, check the logs - https://developers.cloudflare.com/workers/observability/logging/real-time-logs/
NIn my local wrangler project that is not deployed (yet), is it possible to add a binding to some Worker that is already deployed (so I can make RPC calls from the local project to the deployed worker)?
HResponses from Workers, or
fetch
HThey are not.
node_compatnodejs_compatnode_compat
Bit should always be set yes. you cant even override that header
HLooks like it is set to 0?
HAt least at a cursory glance...
Boh you mean requests to workers nvm then
HAt least when I use postman, and toggle the
content-length offBwhy is duration even measured in GB-s ? isn't it more intuitive to measure in pure seconds and just account for 128mb-s, is it because cloudflare is trying to align with other cloud providers standards or like they are trying to make it confusing ?
WOther providers use that and we previously did too (for Unbound), we're moving to Standard so duration isn't even a metric that will be billed on soon enough (for most customers it isn't already)
Bwait so standard usage model doesnt bill on duration at all?
Wnope
Wstandard is requests + cpu time
