Cache-Control response header not change after use cacheSeconds property in the @builder.io/sdk

Bugs
1

I have the problem with Cache-Control response header.

I use the @builder.io/sdk@2.2.2 and i try to fetch builder content by the builder.getAll method.

I set cacheSeconds property to 10, but when the response is incoming the Cache-Control was setting with following property:

image
image1124×132 8.97 KB

But when I set the cacheSeconds property by value greater than 60 the Cache-Control header was changing and max-age ans s-maxage properties have the provide cacheSeconds property value.

Can you have any idea how to use cacheSeconds property with value less than 60?

2

Hello @wojciech.kusmierczyk,

Thank you for flagging this issue. We’ve escalated it to our team for investigation, and we’ll keep you updated on any progress we make.

Thanks,

3

@manish-sharma what is the status of this issue?

4

Hello @wojciech.kusmierczyk,

We are still investigating this issue. Rest assured, I will keep you updated with any progress made.

Thank you for your cooperation.

Best regards,

1 Like
5

Hello @manish-sharma,

Is there any update on this? I might have the similar issue on my end as well. Thanks.

6

Hello @tlee-pb,

I understand the reported issue is causing inconvenience. Rest assured, we have scheduled it for investigation and a possible fix in the 3rd week of August.

Until then if it works, we recommend using cachebust option

const content = await builder
    // Get the page content from Builder with the specified options
    .getall(builderModelName, {
      enrich: true,
      cachebust: true,
    })

Thank you for your patience.

7

I’m still seeming this behaviour, any news on fix?