how do you all do logging?
how do you all do logging?
Ahttps://developers.cloudflare.com/workers/observability/logs/workers-logs enable them and you’ll get them in the dash + filter (free allowance / free in beta + then a cost associated after beta)
Cloudflare Docs
Store, filter, and analyze log data emitted from Cloudflare Workers.
DDoes workers support NextJS API Route?
S@devcat Pages does
DI checked, workers also does. My mistake was to export edge const. But this option is experimental now, under active development
HRequests that match an Asset will be served directly with the asset, bypassing your Worker
LA little confused on when to use a Cloudflare Wrangler Worker vs Cloudflare Pages.
Currently I have one Rust Wrangler worker which acts as a API. I have a Svelte + WebAssembly (with Wasm-bindgen) Page which contacts this API client-side and displays the data on a neat Svelte frontend.
I need to now add another large feature to the API, but it's in Typescript. Can a Rust Wrangler worker run both Rust and Typescript code, or should I create a file on my Page and host the API server that way? Not sure what the proper way to do this is, but I intended the API to be a separate application than the Svelte frontend I have.
Let me know if you need clarification or have a recommendation.
Currently I have one Rust Wrangler worker which acts as a API. I have a Svelte + WebAssembly (with Wasm-bindgen) Page which contacts this API client-side and displays the data on a neat Svelte frontend.
I need to now add another large feature to the API, but it's in Typescript. Can a Rust Wrangler worker run both Rust and Typescript code, or should I create a file on my Page and host the API server that way? Not sure what the proper way to do this is, but I intended the API to be a separate application than the Svelte frontend I have.
Let me know if you need clarification or have a recommendation.
LCan I drill down further? Because this doesn't really help me in explaining what part of the site is responsible for this.
CEither with Workers Logs / obs (lets you see/filter on url) or with the per website / zone analytics, Pro or higher has Web Traffic Analytics which lets you really scope in
LDO you have a link, can't really seem to find it ... It's a Pages project.
Coh opps I didn't look too closely at the UI, there's no workers logs for pages functions. Only native option would be Pro or higher's Web Traffic Analytics, assuming the traffic is through a Pages Custom Domain: https://dash.cloudflare.com/?to=/:account/:zone/analytics/traffic
You can filter/see by path.
Otherwise you'd need to build your own. Free plan has Analytics Engine for free up to 100k writes per day, could write the path and such to it. Or use something else on the free plan like D1, etc. But eitherway no native way to see which paths are being requested outside of Web Traffic Analytics
You can filter/see by path.
Otherwise you'd need to build your own. Free plan has Analytics Engine for free up to 100k writes per day, could write the path and such to it. Or use something else on the free plan like D1, etc. But eitherway no native way to see which paths are being requested outside of Web Traffic Analytics
CIs there any step i am missing from making subdomain.client.com pointing to client.app.mysass.com .. i already created the custom domain and added on client dns, however i'm getting connection timeout
HCan someone help me figure out how to implement cache for a token request (POST) made to an external API within the worker function?
e.g. I'm making a POST request to an external API https://example.com/token within my worker, I can specify the expiration in seconds in the body of this POST request. It then returns access token and field in seconds. I'm looking to cache this token and use the field to calculate whether to return the same token or make a new request to create a new token and then cache that new token instead.
e.g. I'm making a POST request to an external API https://example.com/token within my worker, I can specify the expiration in seconds in the body of this POST request. It then returns access token and field in seconds. I'm looking to cache this token and use the field to calculate whether to return the same token or make a new request to create a new token and then cache that new token instead.
Awhy
this is such a random limitation
this is such a random limitation
AAlso, why is that second sentence there, it has nothing to do with sending emails. "You can't send emails. Instead, you can recieve emails!"
Does anyone know of any workarounds that doesnt include adding a third party to my spf? (please ping me if you reply)
Does anyone know of any workarounds that doesnt include adding a third party to my spf? (please ping me if you reply)
AI have done this. When getting a token, I store it in KV (using KV's feature to automatically expire keys), and also use the Cache API to reduce requests to kv.
So when a request comes in that would require the token, I first check the cache api, then KV (if its in kv then I add it to the cache api before returning), and if its not in either of those then I go and fetch the token, then store it in kv&cache.
Using the cache api is optional, I just use to to reduce requests to KV (therefore, cost)
So when a request comes in that would require the token, I first check the cache api, then KV (if its in kv then I add it to the cache api before returning), and if its not in either of those then I go and fetch the token, then store it in kv&cache.
Using the cache api is optional, I just use to to reduce requests to KV (therefore, cost)
WNot really but using a proper mail provider is the way to go. Cloudflare isn't one
Ayes, which is why i want to use smtp. to use a mail provider to send email
Ais there some reason for blocking this that im missing?
Cit's a super common restriction to prevent abuse
Cfor mail submission there are other ports which are usually used like 587
Ais smtp not email submission? now im confused
CThese days, port 25 is mainly used for SMTP Relaying – transmitting messages between different email servers. It’s not recommended to use for email submission unless you specifically manage your own mail server.https://mailtrap.io/blog/smtp-ports-25-465-587-used-for/
Aahhhh
Athat makes sense, sorry for my confusion. So my usecase would work?
Asending mail using a mail provider through smtp?
CAs long as you don't use that port. Typically mail wouldn't be send that way via Workers though, you'd use a REST/HTTP API. Otherwise for raw tcp, You'd have to find some library that works with Cloudflare's non-standard tcp socket api (or could be hacked into working)
Amy mail provider doesnt provide an http api unfortunately, that was one of the first thing i checked for. Are you aware of any smtp apis for workers?
Ai tried searching myself, but i could only find stuff talking about mailchannels
Cmailchannel's worker integration is dead and it was http/rest api anyway. I'm not aware of any smtp libraries that work with Workers no, I also haven't really gone out of my way to look. Not sure how complex SMTP is, espec with its weird tls stuff
Aoh wow its dead? makes sense, it didnt feel very permenant when it was announced 
thank you for your help
thank you for your help
Cyup: https://community.cloudflare.com/t/mailchannels-end-of-life-notice-migrate-now/658638
There is a few http/rest api options linked there as well like postmark/sendgrid/resend, if you're not stuck with your current
There is a few http/rest api options linked there as well like postmark/sendgrid/resend, if you're not stuck with your current
XEverybody just uses HTTP APIs, but I think in theory if you were really dedicated, and your provider supported a port besides 25, you could write your own SMTP client using Worker TCP https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/
The Cloudflare Blog
Today, we are excited to announce a new API in Cloudflare Workers for creating outbound TCP sockets, making it possible to connect directly to databases and any TCP-based service from Workers.
XPath of least resistance might be to adapt an existing SMTP library to the Worker's TCP API
Ayeah thats my current plan. Doing some more research to be sure theres not an already existing one for workers
XThat is, overall however, not the easiest solution. That is just switching to any other provider, most of whom have a REST API
XIf you're that set on using your specific SMTP-only provider, another option is hosting an SMTP proxy server on some $5 VPS and then calling that via HTTP from your worker
Athat also crossed my mine, but im not sure i want to maintain another microservice outside of cloudflare just for proxying stuff from cloudflare. Although I also probably dont want to maintain a smtp library. I'll look at how complicated smtp libraries are and go from there
XI'd agree with you there. I'm not sure if you have a specific reason for wanting to keep with your current providers, but the options are probably endless, 99% with HTTP APIs
HThanks @ajgeiss0702. Just to confirm, you implemented the cache API on the request being sent to KV, or were you referring to caching the external API request? Any chance you have a code sample that you can share?
AI am putting the token into the cache api, then checking that before checking for the token in KV
Agive me a minute to find that code
Aah unfortunately that specific implementation is not open sourced currently, but its basically this for checking using the cache api:
and for storing the response in the cache api:
theres some conversion stuff there because miniflare's response object doesnt match the web api, but you might not have to deal with that depending on what youre doing
and for storing the response in the cache api:
theres some conversion stuff there because miniflare's response object doesnt match the web api, but you might not have to deal with that depending on what youre doing
H@ajgeiss0702 Thank you so much. I'll try to follow this approach for my use-case. Really appreciate the help!
SRebuild feature is very helpfull
Phey! does anyone knows why when testing a service worker in localhost gives me this error:
but when deploying the exact same code to a worker and testing it, works fine? Iwrangler 3.4.0`
but when deploying the exact same code to a worker and testing it, works fine? Iwrangler 3.4.0`
SI don't want to have sensitive information (api key, etc.) in wrangler.toml, so I am running a shell in the build command that dynamically creates wrangler.toml from the build variables and runs wrangler deploy using that wrangler.toml.
How does everyone protect their sensitive information?
How does everyone protect their sensitive information?
HYou shouldn’t be putting sensitive info in your wrangler.toml. Secrets can be deployed separately
SThank you very much! Yes, I know. So I have created wrangler.toml.template and run the build command to generate the wrangler.toml file shell with the build variables.
You can also refer to the values registered in github actions secrets in the secrets property of github actions, but I think it will be difficult to manage if you register PRD_API_KEY, STG_API_KEY, etc. for each environment. So I have Cloudflare Workers (PRD, STG, E2E, Test, etc...) created for each environment. I register environment variables in the build variables of What do you think about this solution?
You can also refer to the values registered in github actions secrets in the secrets property of github actions, but I think it will be difficult to manage if you register PRD_API_KEY, STG_API_KEY, etc. for each environment. So I have Cloudflare Workers (PRD, STG, E2E, Test, etc...) created for each environment. I register environment variables in the build variables of What do you think about this solution?