Talk:Web cache
From Wikipedia, the free encyclopedia
How does a web browser decide if the version in its internal cache is up to date? - Omegatron 16:30, July 20, 2005 (UTC) Pfgfffffffffffffffffffffffffffff
- While some content has an explicit expiry-time set, in most cases the browser sends a special If-Modified-Since-Request to the Webserver, which replies either with a status code indicating that the browsers copy is still 'fresh' or with the updated content. --Drangon 22:43, 23 July 2005 (UTC)
A "transparent" cache in HTTP is semantically transparent. What some people mean when they say "transparent proxy" is an interception proxy. This is well-known and agreed upon in the HTTP caching community.
Similarly, the most applicable term for a "reverse" proxy in HTTP is "gateway."
It's important to keep this article focused on caching, not proxies. Also, it's important to make sure it doesn't become a billboard for any particular vendor (which is why I removed the product listing, as one particular product keeps on being aggressively added.)
Cheers
mnot 13:50, 9 May 2007 (UTC)
Redundant link to www.Web-Cache.com[1] removed from the references
Prasanna 07:18 PM, September 08 2007 (IST)
[edit] Google Cache
Why does google cache redirect here if there is no mention in the article. If it is ok with people I will remove the redirect. Robotboy2008 (talk) 22:54, 4 December 2007 (UTC)
[edit] Split and merge
I think that the parts of this article dealing with client-side caches should be split into a new article (browser cache is currently a redirect here). If we do that, we should merge in Temporary Internet Files, which is just the Internet Explorer instance of a browser cache. « Aaron Rotenberg « Talk « 01:23, 4 May 2008 (UTC)
