Anyone used the `Etag` response header inside a Next.js Application?
I am using a getServerSideProps that renders some HTML on the server but everytime I make a request to my Next.js Application a new Etag is generated even tho' the contents are the same. I'm pretty sure it has something to do with getServerSideProps and I would like to keep it that way because I need some send some responses back in case of a business logic is met
0 Replies