use

tee()

on the

body

object and that'll give you two streams

you'd probably want to do the cache put in a waituntil

otherwise you're only reading one stream at a time & causing buffering

with tee() it seems to be working now, thanks

suddenly been getting a lot of these errors reported in Sentry

Network connection lost.

for our worker, even on routes where we just connect to Durable Objects and not anything like a third-party API (although I realize DO is essentially a third party API). unfortunately there is no stack trace or context on the error. any ideas?

Actually worker serving images from R2 is like 2x faster than using public CDN.

Hi, are you guys using CF Workers as a reverse proxy, or as your only backend? 🙂

sathoro or me?

Just anybody, I'm curious 🙂

both

some just transform a response on top of an existing origin

some are the origin

@kian What's the criteria when you use which? 🙂

just depends if a Worker is fit for the origin - our main apps are Laravel monoliths so Workers could only ever serve as an on-top layer

whereas for a Discord bot that uses application commands, you can run it entirely on Workers

@kian So new system that CF Worker can solve = CF Worker (as your only backend) If not (f.ex. legacy system), then CF Worker as reverse proxy?

hosting a discord bot on workers seems to be possible, what would the limitations of free accounts be to the bot?

It can only do application commands (which are webhooks sent to your Worker via Discord) rather than gateway (which is when your bot subscribes to a WebSocket)

That's not unique to the free plan though

has anyone ran into this error when fetching a site enforcing TLS 1.3 from a worker?

fetch('https://mysite.com')

OpenSSL error; message = error:1000042e:SSL 
routines:OPENSSL_internal:TLSV1_ALERT_PROTOCOL_VERSION

do i have to lower my TLS version to use workers?

not sure if anyone got sha3 working in workers (without using wrangler) i tried used crypto.subtle.digest('SHA-3-256', messageBytes); but it appears this is not implemented yet and it lets me save the code (which is odd usually if this wasnt implemented it wouldn't let me save the code, it crashes the dom lol 😄 anyone have thoughts on getting sha3 - 256 working in workers (without using wranglar 😄 )

Is that a WebCrypto algorithm?

It's not on

SHA-256 and SHA-384 are, but I have no idea what SHA-3-256 is

Ah, yeah - https://github.com/w3c/webcrypto/issues/319

thats the one :D. trying to do a merkle tree in cloudflare worker (without a wrangler) and its driving me crazy 😄

literally one command away and i might have to break out wrangler 😄

Any way to detect if google bot (or other crawler) inside worker?