Cloudflare

but can you create a response with readableStream?

hey master <@883084594218430464> , since you're around, 
you have been able to somehow to communicate betweet two custom domain workers, 
any chance for a gist? 
I'm losing my mind on this issue of 522 and you posted before that it worked for your example

> any chance for a gist? 
Just two Workers with custom domains - nothing more

```toml
[route]
pattern = "custom-a.blah.com"
custom_domain = true
```

```yml
Cloudflare DNS: content-length: 45
No Cache DNS: content-length: 45
Cache DNS: content-length: 55
```

and this added content from cache api seems to break DNS.

Gah that's literally what I have up
2 workers with one calling the second one. and I get a 522. 

Could this be per account? 🤯

I think caching a DoH response from cloudflare-dns.com within a Worker makes no sense

2023-02-18-22-44-02

Cache on workers.dev isn't documented to work

Maybe try running it with `wrangler dev --local`

I don't think you'd be more than 3-5ms behind by fetching every time - and by that point _why_ create "your own" DoH worker anyways if you're just caching/returning another value 😅

it does cache content, but somehow it gets bigger response?

Am I reading it wrong? It looks like `workers.dev`

image

I don't do local development anymore for workers

Oh I'm dumb. I didn't see you are using publish each time

hahaha project has not been released yet XD

I’m confused. What is the benefit supposed to be here?