# Proper usage of proxy\_store, proxy\_cache\_path

**URL:** <https://www.ruby-forum.com/t/proper-usage-of-proxy-store-proxy-cache-path/193761>\
**Category:** NGINX\
**Created:** [August 24, 2010, 1:11am UTC](https://www.ruby-forum.com/t/proper-usage-of-proxy-store-proxy-cache-path/193761 "2010-08-24T01:11:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Trainor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ed8c4c/32.png) [@Dan\_Trainor](https://www.ruby-forum.com/u/Dan_Trainor)\
**Post date:** [August 24, 2010, 1:11am UTC](https://www.ruby-forum.com/t/proper-usage-of-proxy-store-proxy-cache-path/193761/1 "2010-08-24T01:11:53Z")

</div>

Hello -

I was doing some experimenting and came across proxy\_store as part of  
Nginx’s HTTP Proxy Module I was able to implement it in my testing  
environment, and it operated exactly as I expected it to. It was nice  
to see how it worked.

I’ve stumbled upon proxy\_cache\_path, but I don’t quite understand  
exactly how it works. I expected it to work in a similar method as to  
how proxy\_store would work, but maybe with more granular controls on  
exactly how the content is stored.

Althogh I’ve read through HTTP Proxy Module documentation several  
times, I’m still lost on a clear knowledge between the two directives,  
how they should be used, when and where, and how I can exploit them to  
achieve my goal.

If at all possible, can someone please take a moment to help clear  
this up for me?

Thanks!  
-dant