search

GUI / http-stale-cache-proxy

A non-compliant HTTP caching proxy that excels at serving stale cached content, while keeping its cache updated asynchronously.
MIT License
15 stars 5 forks source link

false responses in Virtual Hosting-Environment #1

Closed DonatelloXX closed 10 years ago

DonatelloXX commented 10 years ago

If changeOrigin is set to false then all requests are forwarded with thier original names to the target. But caching seems to affect only Url Paths - not domains.

1) Client requesting h1.example.com/test.htm -> request forwareded to target squid.example.com and returning proper content.

2) Client requesting h2.example.com/test.htm -> request served by cache and returning content of h1.example.com/test.htm, Asynchronously refreshing response.

3) Client requesting h1.example.com/test.htm -> request served by cache and returning content of h2.example.com/test.htm, Asynchronously refreshing response.

Do i have to run a Instance of http-stale-cache-proxy for every virtual webhost? Or will it be possible to store/retrieve cache-Objects with correct domainnames?

GUI commented 10 years ago

I'm sorry for the long delay. The hostname wasn't be used when calculating the cache key, so the cache wasn't unique across different domains. I believe this should be fixed in v0.2.0 that I just pushed live.