Title: Forward request header without caching it
Last modified: November 20, 2023

---

# Forward request header without caching it

 *  Resolved [George-Paul Crețu](https://wordpress.org/support/users/necroob/)
 * (@necroob)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/)
 * Hi there,
 * I have a setup where I need users from a certain country to be redirected on 
   a certain page.
 * The tech stack includes AWS CloudFront which passes along a request header “CloudFront-
   Viewer-Country” that has the country code in ISO format, and that is great.
 * The problem I’m having is that it gets cached and I can’t use it to create the
   logic I need.
 * For the first use that lands on the page, it’s ready correctly, but it gets cached.
   The next user that lands on the same page will have the same value as the first
   one. Without caching works ok.
 * No, I can’t turn off cache for that particular page because it should work no
   matter on what page they land.
 * Does W3TotalCache have a way to pass that value without caching it?
 * I know that another solution will be to have CloudFront pass that as a response
   header in the browser, but that is a workaround.
 * Thanks a lot!
 * George

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/#post-17216232)
 * Hello [@necroob](https://wordpress.org/support/users/necroob/)
 * Thank you for reaching out and I am happy to help!
   Let me check this more and
   investigate and I’ll get back to you with more information.
 * Thanks!
 *  Thread Starter [George-Paul Crețu](https://wordpress.org/support/users/necroob/)
 * (@necroob)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/#post-17238375)
 * Hi [@vmarko](https://wordpress.org/support/users/vmarko/)
 * Any update on this?
 * Thanks a lot!
 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/#post-17280383)
 * Hello [@necroob](https://wordpress.org/support/users/necroob/)
 * Sorry for the late reply.
   This is not possible in the W3TC settings, however,
   you may want to try adding a rule above the W3TC and see if this helps
 * Please check more in the link below 👇
 * [https://serverfault.com/questions/357716/can-apache-conditionally-perform-a-rewrite-from-a-custom-http-header](https://serverfault.com/questions/357716/can-apache-conditionally-perform-a-rewrite-from-a-custom-http-header)
 * Thanks!
 *  Thread Starter [George-Paul Crețu](https://wordpress.org/support/users/necroob/)
 * (@necroob)
 * [2 years, 5 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/#post-17286281)
 * Hi [@vmarko](https://wordpress.org/support/users/vmarko/),
 * Thanks for the update.
 * That’s an interesting suggestion. We went with a different approach to solve 
   this.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Forward request header without caching it’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [George-Paul Crețu](https://wordpress.org/support/users/necroob/)
 * Last activity: [2 years, 5 months ago](https://wordpress.org/support/topic/forward-request-header-without-caching-it/#post-17286281)
 * Status: resolved