Ben Comments - Answer Overflow

Ben

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

Wow that worked If I had sent username:password in that request, thinking it was encrypted because it was to https:// Cloudflare would have actually turned that off and sent my request across the internet in the clear. This is actually a pretty bad thing, yeah?

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

And this setting is Flexible by default!?!?

Current encryption mode:

Flexible
The encryption mode was last changed 2 months ago.

Your encryption mode is set to Cloudflare’s recommendation. Override this by switching to custom.

Current encryption mode:

Flexible
The encryption mode was last changed 2 months ago.

Your encryption mode is set to Cloudflare’s recommendation. Override this by switching to custom.

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

Let me find this setting...

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

What!? You're saying a setting that I didn't know existed was forcibly removing encryption and security from my stack without me knowing??

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

Leo; I'm sorry, I don't quite understand; I'm not that familiar with the cloudflare settings Do you mean to change settings on the pages domain 'foo.domain.com' , which has the worker mounted under it, or foo-api.domain.com, which the worker is fetching? Either way, I don't quite see the relationship. If you are thinking this is a 307 redirect to force http->https; that shouldnt be happening becasue both requests are being explicitly made with https:// protocols, that would only make since if the fetch request were ignoring the protocol , as my Request object is being explicitly stated as https://foo-api.domain.com That would indicate a bug in my opinion - if fetch were indeed making an http request and getting 307'd, and an even bigger bug that the Request object fails to follow the redirect - if I set redirec follow the request fails with "too many redirects" which means it has gotten itself into a loop.

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

I tried moving my domain management away from cloudflare to godaddy but no luck.

8 replies

CDCloudflare Developers

•Created by Ben on 11/2/2024 in #pages-help

Bug: Fetch() returns nonsense 307 when called under a pages domain

Here's a ray Id of an example if it helps: 8dc4ad61f7d5bcc6-ATL

8 replies

Gaming

Programming