Cloudflare Developers•3y ago

Should I create a account-related ticket in this case or do you think this might be a dead-end for n

Should I create a account-related ticket in this case or do you think this might be a dead-end for now?

Erisa•1/9/23, 11:41 AM

Free being the zone/website plan of Free/Pro/Business/Enterprise

Kkev-ac Should I create a account-related ticket in this case or do you think this might...

Erisa•1/9/23, 11:41 AM

It may be a deadend if youre on free tbh, not sure we would do this

Erisa•1/9/23, 11:42 AM

We can definitely remove the restriction if it arises for free users though

kev-acOP•1/9/23, 11:44 AM

Our current use-case does not justify a paid zone plan tbh. Paid workers/r2 etc. yes, but not for the zone.

Erisa•1/9/23, 11:45 AM

Thats fair

Erisa•1/9/23, 11:46 AM

A lot of people upgrade to Pro for improved analytics or to get support, but if you dont need those its fair enough to stick to free

Erisa•1/9/23, 11:46 AM

support outside of me being here in my free time anyway notlikemeow

EErisa A lot of people upgrade to Pro for improved analytics or to get support, but if ...

kev-acOP•1/9/23, 11:48 AM

If the plans would be an account-thing I might be able to justify it, but as we use domains to separate some parts of our application we would need to pay x-times.

Erisa•1/9/23, 11:49 AM

Yeah some features like support are applied account-wide

Erisa•1/9/23, 11:49 AM

But the improved analytics would only be for the zone indeed

Original message was deleted

kev-acOP•1/9/23, 11:50 AM

But not the feature-set like Cache analytics etc.

kev-acOP•1/9/23, 11:50 AM

Which would be my main "selling point" internally.

kev-acOP•1/9/23, 11:50 AM

It's always hard to justify the need for support internally if we don't always need it.

kev-acOP•1/9/23, 11:52 AM

That being said, thanks for your help and time @Erisa | Support Engineer!

Erisa•1/9/23, 11:53 AM

I see a lot of customers who upgrade to Pro the first time they need support just so they can open a ticket, who would be on free otherwise

Erisa•1/9/23, 11:53 AM

I wonder how many cancel it when their ticket is over

Kkev-ac I (maybe?) found a bug within the R2 access token logic. Last evening I've creat...

kev-acOP•1/9/23, 11:53 AM

Btw is this the right place to report this bug? The github repo seems the wrong place

EErisa I wonder how many cancel it when their ticket is over

kev-acOP•1/9/23, 11:54 AM

I'm pretty sure you have some internal reports for this exact case

Erisa•1/9/23, 11:54 AM

Honestly true, I should have a look

Kkev-ac Btw is this the right place to report this bug? The github repo seems the wrong ...

Erisa•1/9/23, 11:55 AM

The repo is only for docs so definitely the wrong place, this server or a support ticket are the correct places to report that. Unfortunately we've now had a whole conversation so the R2 team might not see it

EErisa The repo is only for docs so definitely the wrong place, this server or a suppor...

kev-acOP•1/9/23, 11:55 AM

R2 team, where are you?

Matt Silverlock•1/9/23, 1:15 PM

The best thing to do is to open a Support ticket for these things. Our Support team can then escalate internally / open an internal bug as appropriate

kev-acOP•1/9/23, 1:15 PM

But I can't open a ticket as I'm on the Free plan.

Matt Silverlock•1/9/23, 1:16 PM

(Also keep in mind this entire chat happened over a weekend)

MMatt Silverlock (Also keep in mind this entire chat happened over a weekend)

kev-acOP•1/9/23, 1:17 PM

I'm not expecting any SLA or response times. It's just a bug I've found which I think could be nice to know for the R2 team.

Kkev-ac I'm not expecting any SLA or response times. It's just a bug I've found which I ...

Matt Silverlock•1/9/23, 1:20 PM

Right, totally appreciate that! But also just setting expectations. I’ve raised the access token issue internally. It won’t just impact R2, if the bug indeed exists (not able to repro just yet)

MMatt Silverlock Right, totally appreciate that! But also just setting expectations. I’ve raised ...

kev-acOP•1/9/23, 1:21 PM

I've created a new 24-hour access token today to continue my work. If it happens again this midnight I can update you here. Then I would have reproduced it, at least for my account.

kev-acOP•1/9/23, 1:24 PM

@elithrar Do you need any info from my side to help narrowing it down? (Oops, wrong mention)

Kkev-ac @elithrar Do you need any info from my side to help narrowing it down? (Oops, w...

Matt Silverlock•1/9/23, 2:32 PM

Account ID and token ID (not the actual secret) would be great. I also assume it’s midnight UTC (hard to scroll back in this convo…) you’re seeing it expire?

MMatt Silverlock Account ID and token ID (not the actual secret) would be great. I also assume it...

kev-acOP•1/9/23, 2:38 PM

Just sent you the details in a PM. Timestamp according to the Audit Log was 2023-01-09T01:00:57+01:00.

JJeff Is there a way to get the folder size?

Vero•1/9/23, 4:11 PM

Hey @j3fftw . Currently, there's not any great way to do that beyond listing all the files which start with the same prefix and summing the file size of each one

MMatt Silverlock Account ID and token ID (not the actual secret) would be great. I also assume it...

kev-acOP•1/10/23, 9:15 AM

Followed up with you in PM, but wanted to update the channel here too, just in case somebody else finds this later. It happened again this midnight for a 24-hour token.

Epailes•1/10/23, 1:19 PM

I tried having a search around but am I right in saying that there's no replication for R2 at the moment, but some form of redundancy/replication is on the roadmap?

sakuta•1/10/23, 4:49 PM

how can i allow only access to a specific bucket for an api token? (using s3 api, not workers binding)

sakuta•1/10/23, 4:49 PM

and not access to all buckets in my account

kian•1/10/23, 4:52 PM

Not possible currently

kian•1/10/23, 5:20 PM

- await env.PROFILE.put('do-something', file);
+ await env.PROFILE.put('do-something', file.stream());

- await env.PROFILE.put('do-something', file);
+ await env.PROFILE.put('do-something', file.stream());

kian•1/10/23, 5:23 PM

Depending how the uploads are taking place, it's preferred to send the file's binary content as-is in the request body & stream that into R2 so that you're not buffering the file into the Worker's memory which can cause resource exhaustion if there's large enough files in concurrent requests - but if you're using something like a HTML

<form>

<form>

then you'll probably have to stick with FormData.

kian•1/10/23, 5:23 PM

.put

.put

's third argument, options, is how you can specify

content-type

content-type

and whatnot to be stored with the object so that they're properly presented when viewed in a public bucket and the like.

kian•1/10/23, 5:28 PM

Basically

--data-binary

--data-binary

in cURL or just

binary

binary

in Postman's body options.

interface Environment {
    R2: R2Bucket;
}

export default <ExportedHandler<Environment>>{
    async fetch(req, env) {
        if (req.method !== 'POST') {
            return new Response('Method Not Allowed', {
                status: 405,
                headers: {
                    Allow: 'POST',
                },
            });
        }

        const url = new URL(req.url);
        const path = url.pathname.slice(1);

        try {
            await env.R2.put(path, req.body, {
                httpMetadata: req.headers,
            });

            return new Response(`Successfully uploaded ${path}`);
        } catch (e) {
            return new Response(`Failed to upload ${path}`, {
                status: 500,
            });
        }
    },
};

interface Environment {
    R2: R2Bucket;
}

export default <ExportedHandler<Environment>>{
    async fetch(req, env) {
        if (req.method !== 'POST') {
            return new Response('Method Not Allowed', {
                status: 405,
                headers: {
                    Allow: 'POST',
                },
            });
        }

        const url = new URL(req.url);
        const path = url.pathname.slice(1);

        try {
            await env.R2.put(path, req.body, {
                httpMetadata: req.headers,
            });

            return new Response(`Successfully uploaded ${path}`);
        } catch (e) {
            return new Response(`Failed to upload ${path}`, {
                status: 500,
            });
        }
    },
};

kian•1/10/23, 5:29 PM

That'll take a binary sent to

https://example.com/dog.png

https://example.com/dog.png

and upload it to R2 as

dog.png

dog.png

kian•1/10/23, 5:30 PM

I'm not sure I follow what you mean by over JSON

kian•1/10/23, 5:31 PM

You'd just send the file's raw content as-is as the body

interface Environment { R2: R2Bucket; } export default <ExportedHandler<Environment>>{ async fetch(req, env) { if (req.method !== 'POST') { return new Response('Method Not Allowed', { status: 405, headers: { Allow: 'POST', }, }); } const url = new URL(req.url); const path = url.pathname.slice(1); try { await env.R2.put(path, req.body, { httpMetadata: req.headers, }); return new Response(`Successfully uploaded ${path}`); } catch (e) { return new Response(`Failed to upload ${path}`, { status: 500, }); } }, };

Should I create a account-related ticket in this case or do you think this might be a dead-end for n

Similar Threads

Similar Threads

Similar Threads