Is DO LoadBalancer adding `cache-control: private` header when using sticky sessions?

I’m currently using sticky sessions with DO LoadBalancer and found that there is cache-control: private header added to the end of response headers which is breaking my caching policies:

set-cookie: XXXX=node-XXX|XXX|XXX; path=/; SameSite=Lax
cache-control: private

Maybe that’s not related to sticky sessions but I would like to get rid of that header. I’ve tried removing several upstream headers and also adding explicit cache-control and expires headers but no luck.

Is there a config option for that or something I can do myself?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Here too this can be it. I’m currently using sticky .

It looks like it started in the last load balance updates.

This is very bad as it modifies an application response.