ale Comments - Answer Overflow

ale

Posts Comments

CDCloudflare Developers

•Created by krizh on 7/25/2024 in #pages-help

I am trying to delete few cloudflare pages but I keep getting An unknown error occured.

hi Christopher, you should soon receive an email from Support to keep track of your case

12 replies

CDCloudflare Developers

•Created by Tobias on 7/24/2024 in #pages-help

Trying to delete a cloudflare pages project

hi Tobias, we've opened a Support ticket for this case. You should soon receive an email with information to keep track of it

8 replies

CDCloudflare Developers

•Created by Jack RED on 3/5/2024 in #general-help

cpu_ms_limit_not_allowed_for_usage_model

Hi, hi Jack, it's Ale from Support here at Cloudflare. I've opened a ticket to keep track of it and we are currently reviewing it with Engineering

15 replies

CDCloudflare Developers

•Created by BIGJ on 11/9/2023 in #pages-help

Account issues

hi, hi @BIGJ. I've opened a Support ticket for you, you should have received an email about it

15 replies

CDCloudflare Developers

•Created by Niceman on 7/3/2023 in #r2

Hello I m trying to upload a file with a

Hi, hi Niceman 👋 Are you still seeing this error? If so, how are you generating the pre-signed URL and what is the request that is causing this CORS error?

2 replies

CDCloudflare Developers

•Created by daniel_klungo on 7/4/2023 in #r2

Express ish Next js API routes

fetch can throw exceptions (https://developer.mozilla.org/en-US/docs/Web/API/fetch#exceptions) you can reproduce it running the following code:

const f = async () => {try { await fetch('https://cloudflare.com')} catch (e) { console.log('err')} };
f();

const f = async () => {try { await fetch('https://cloudflare.com')} catch (e) { console.log('err')} };
f();

But yes, it's just a suggestion (:

4 replies

CDCloudflare Developers

•Created by daniel_klungo on 7/4/2023 in #r2

Express ish Next js API routes

will create a thread so we can keep the channel tidy. I was able to replicate the CORS error that you saw. However, at least in my case, a 403 also happened and, as you mentioned, removing the hash sums validations, it gets resolved. So yes, you do get an error when there is a hash mismatch, but it seems that the response might be missing some CORS headers that would allow you to see it in a normal response. I can suggest wrapping the fetch within a try/catch block so you can define what to do if these requests fail.

let res;
try {
  res = await fetch(prefetchURL, {body:object ,method:'PUT'}) 
} catch (err) {
  // Error handling in case of failure to upload object
}

let res;
try {
  res = await fetch(prefetchURL, {body:object ,method:'PUT'}) 
} catch (err) {
  // Error handling in case of failure to upload object
}

I'll also ask internally on why these errors don't seem to have the same Access-Control-Allow-Origin as the Bucket's CORS policy

4 replies

Gaming

Programming