Title: HTTP Headers
Last modified: August 22, 2016

---

# HTTP Headers

 *  [cbunting99](https://wordpress.org/support/users/cbunting99/)
 * (@cbunting99)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/http-headers/)
 * I noticed when testing a site’s http headers on redbot.org, that the client side
   cache settings, whether you turn them on or off, affect or override the headers
   we have set in the nginx.conf or the virtual hosts.
 * I was going to use this on a small site that I was working on, but there should
   be an override to the client side caching to a null value, instead of returning
   Pragma: no-cache as it’s depreciated!
 * Chris
 * [https://wordpress.org/plugins/quick-cache/](https://wordpress.org/plugins/quick-cache/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/http-headers/#post-5465032)
 * Hi Chris,
 * Apologies for the delayed response. I’ve opened a feature request to make it 
   possible to supply your own headers: [https://github.com/websharks/quick-cache/issues/371](https://github.com/websharks/quick-cache/issues/371)

Viewing 1 replies (of 1 total)

The topic ‘HTTP Headers’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/quick-cache_efefef.svg)
 * [Quick Cache (Speed Without Compromise)](https://wordpress.org/plugins/quick-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/quick-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/quick-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/quick-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/quick-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/quick-cache/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/http-headers/#post-5465032)
 * Status: not resolved