<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-33798166</id><updated>2011-08-24T06:50:05.677Z</updated><title type='text'>Web Cache Logs</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>8</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-33798166.post-115892096758656007</id><published>2006-09-22T10:28:00.000Z</published><updated>2006-09-22T10:29:27.596Z</updated><title type='text'>activity log, to do list</title><summary type='text'>Now my test pages have a how to and a much more intuitive interface: to figure what's going on there is no need to trace http headers, just watch the image — it is intended to change only when cache is not used. Also a reason to believe for my anti-msie friends was included. Before moving on to [script generated] dynamics the following tests will be done: Expires with no validator Last-Modified </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115892096758656007/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115892096758656007' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115892096758656007'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115892096758656007'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/activity-log-to-do-list.html' title='activity log, to do list'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115853865910694695</id><published>2006-09-18T00:16:00.000Z</published><updated>2006-09-19T21:36:06.210Z</updated><title type='text'>META cache</title><summary type='text'>This should be a post about using the html tag META with an equivalent to Expires to define an expiration time. But that makes no sense in most situations! Usually we want to say "check this every day" or "every 5 minutes" and that implies an expiration time relative to last access, something we can't do with META Expires — only absolute expiration times are possible. So it's time to move on. </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115853865910694695/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115853865910694695' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115853865910694695'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115853865910694695'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/meta-cache.html' title='META cache'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115820156542540013</id><published>2006-09-14T02:38:00.000Z</published><updated>2006-09-14T02:39:25.436Z</updated><title type='text'>setting Expires with web server</title><summary type='text'>Expiration date can be set in web server configuration for static resources [dynamic resources can have Expires set by scripts]. Apache Expires can be set in the configuration file [httpd.conf] or with .htaccess files. In any case expires_module must be active. While .htaccess files are more flexible, allowing changes without server restart [and sometimes are the only choice available], there is </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115820156542540013/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115820156542540013' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115820156542540013'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115820156542540013'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/setting-expires-with-web-server.html' title='setting Expires with web server'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115791461236999437</id><published>2006-09-10T18:56:00.000Z</published><updated>2006-09-15T19:16:05.476Z</updated><title type='text'>Old style cache control</title><summary type='text'>What if you want your page to be checked once per day, whatever are browser settings? Or every time the page is visited, although this is a bad idea for statics? HTTP/1.0 has the Expires clause, that allows web servers to specify a date/time after which the entity should be considered out of date and checked by browsers. Using Expires  the web designer can control how fresh each entity is, </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115791461236999437/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115791461236999437' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115791461236999437'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115791461236999437'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/old-style-cache-control.html' title='Old style cache control'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115782613926519037</id><published>2006-09-09T18:21:00.000Z</published><updated>2006-09-09T21:19:28.303Z</updated><title type='text'>browser cache strategy</title><summary type='text'>Opera [7.5] is very straightforward: for pages without explicit expiration it checks at regular, configurable periods of time starting on last check. Explorer [6.0] has 4 options: ever, never, per start or default. Per start means per instance: open other window and all stuff will be checked again. Default seems to be per start plus some heuristic checks, for entities without expiration. Netscape</summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115782613926519037/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115782613926519037' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115782613926519037'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115782613926519037'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/browser-cache-strategy.html' title='browser cache strategy'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115766981983395859</id><published>2006-09-07T22:56:00.000Z</published><updated>2006-09-08T12:54:16.766Z</updated><title type='text'>Woow, how time flies!</title><summary type='text'>This blog thing took me a big time with the template. Now main block and sideboard are adjustable to window width, with a max-width working in IE thanks to Svend Tofte — I dont like style hacks but this one is very clear and makes IE do something that it should be doing lta. Also a nice toggle system for logs was implemented, it is a little fat but allows multiple toggles in one post. Believe me,</summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115766981983395859/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115766981983395859' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115766981983395859'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115766981983395859'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/woow-how-time-flies.html' title='Woow, how time flies!'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115739864409789880</id><published>2006-09-04T19:36:00.000Z</published><updated>2006-09-15T19:14:56.553Z</updated><title type='text'>Simple things first</title><summary type='text'>With default configuration web servers and web browsers do a good job keeping "fresh" static documents near you, saving them in computer's hard disk. A web page that, with all related documents, would take one second to be fully downloaded from the web can be retrieved from disk in some milliseconds — about 100 times faster. This can be implemented through HTTP headers or equivalent HTML meta </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115739864409789880/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115739864409789880' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115739864409789880'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115739864409789880'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/simple-things-first_04.html' title='Simple things first'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-33798166.post-115732515152045810</id><published>2006-09-03T23:09:00.000Z</published><updated>2006-09-04T00:46:16.610Z</updated><title type='text'>Web Cache Logs</title><summary type='text'>Computer-related cache technology is the use of a faster and smaller memory type to accelerate a slower and larger memory type. Web pages and other documents are frequently cached closer to the client through browser, proxy, or server caches. By storing frequently accessed documents closer to the client, bandwidth consumption, server load, and latency can be reduced.Usually a cache of recently </summary><link rel='replies' type='application/atom+xml' href='http://webcachelogs.blogspot.com/feeds/115732515152045810/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=33798166&amp;postID=115732515152045810' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115732515152045810'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/33798166/posts/default/115732515152045810'/><link rel='alternate' type='text/html' href='http://webcachelogs.blogspot.com/2006/09/web-cache-logs.html' title='Web Cache Logs'/><author><name>Rui Baptista</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
