Server Side Rendering with Netlify Functions

[ecomplus]

@Dennis

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 received.

Great, it was implemented recently?
When I started using partial build and lambda function for SSR I think I tested it and the page that had been SSRendered continued to deliver the old version.
I was using following Cache-Control:
public, max-age=60, s-maxage=2592000
The expectation is that after a new deploy the page URL hits the lambda function again, would that happen?

Not using any proxy…