I’d love to know if Netlify Functions can be used for server side rendering. This is what needs to happen: Build Netlify runs the build command to generate both the server lamdba and the static files. Netlify uploads the server file (for example /build/server.js) to AWS lambda. Netlify uploads st…

Hey, @Scott , thanks for the answer. Another question: is there a way to invalidate/purge the cache (CDN) via an API request? I mean, other than generating a new build, of course. Just the cache :slight_smile:

Hey @luisherranz , As far as I’m aware, there isn’t – it’s not documented on our open API if there is! :stuck_out_tongue:

Ok, thanks @Scott . Then I guess the only workaround is to set the s-maxage cache-control directive of the HTML files to their maximum (31536000) to make them immutable and use a WordPress plugin that triggers a new build ( Search Results for “netlify” | WordPress.org ) and invalidates the CDN each ti…

@luisherranz , Probably not the best thing to be doing! Our CDN handles expiration normally, you’ll only need to consider revising this if you’ve set anything in your proxy response headers.

Yeah, I guess people could set s-maxage to something like 30 minutes for example, but that would mean the content wouldn’t be instantly updated when a post is published/updated, which is not ideal. I think it’d be better to set s-maxage to the maximum to simulate an immutable, and then trigger the …

I think perhaps you misunderstand how we invalidate cached assets. Have you read this: Better Living Through Caching ? Basically, our CDN relies on filenames remaining the same and the cache-control header that we very intentionally set. To answer your question: no, there isn’t any ‘trigger’ from yo…

[image] Dennis: Basically, our CDN relies on filenames remaining the same and the cache-control header that we very intentionally set. Nice. Thanks for the link :slight_smile: And does that approach work for HTML responses returned by Netlify Functions or just for static HTML files?

@philhawksworth This is brillant! Thanks for sharing it. I just have one question, how would you go about handling if the data on the backend changes? Say the shape or color of the lolly?

[image] Dennis: To answer your question: no, there isn’t any ‘trigger’ from your end to invalidate CDN node cache except through a build/deploy, as this is part of the atomic nature of deploys. Hey @Dennis , any plans to provide this trigger? Imo would be really nice being able to purge cache…

To answer your first question, cache is already purged on each deploy for assets hosted on Netlify. If you are proxying to another URL, we will use whatever caching value that the response gives us, so those assets may not be purged on deploy immediately, depending on the cache-control headers recei…

Server Side Rendering with Netlify Functions

Support

luisherranz August 9, 2020, 9:09pm 22

Nice. Thanks for the link

And does that approach work for HTML responses returned by Netlify Functions or just for static HTML files?

Topic		Replies	Views
Netlify Function with query strings ignores custom Cache-Control header Support lambda-functions	56	8140	October 9, 2024
Functions CDN too slow to update to new commit Support lambda-functions	23	2659	May 11, 2020
Users are being served old static files and old Lambda functions Support deployment , lambda-functions	14	1069	February 21, 2023
Stale-while-revalidate header unexpected behavior Support deployment , lambda-functions , headers	3	928	November 17, 2023
Site going down every 10 minutes Support deployment	54	2190	December 22, 2022

Server Side Rendering with Netlify Functions

Related topics