- Notifications
You must be signed in to change notification settings - Fork 92
Closed
Labels
Description
It seems like the current code is forcing no-cache to be set on Netlify function calls (including getServerSideProps). I think this makes sense in a lot of cases, however we just had a use case where it would be safe to cache the results of that server-side execution for some period of time and we wanted to express that by setting the Cache-Control setting in the getServerSideProps method. This seems to be problematic because next-on-netlify adds an additional no-cache header which conflicts with ours. Is this something that could be conditional on an existence check for the header?