You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that most caching plugins of this nature add an HTML comment such as: <!-- served by Surge: {timestamp of when page was cached} -->
to the end of each page. I was hoping you'd consider adding it here. It would make it easier to verify the cache is working as expected, as well as help debug issues or answer questions about when a page was cached.
Great plugin! It's the first of its kind that I'm giving serious consideration to using in a Production environment.
The text was updated successfully, but these errors were encountered:
Not a huge fan of altering the resulting output. I think I'd rather put more work into the Site Health dashboard for configuration debugging. However, I will certainly consider this for any future updates. Thank you for trying out Surge!
One alternative you can use is the X-Cache header that Surge outputs. It'll have a value of hit, miss, or expired. IMO that's just as easy to see as viewing the source, and I agree w/ Konstantin that it's nice to not alter the output.
I believe that most caching plugins of this nature add an HTML comment such as:
<!-- served by Surge: {timestamp of when page was cached} -->
to the end of each page. I was hoping you'd consider adding it here. It would make it easier to verify the cache is working as expected, as well as help debug issues or answer questions about when a page was cached.
Great plugin! It's the first of its kind that I'm giving serious consideration to using in a Production environment.
The text was updated successfully, but these errors were encountered: