May 10, 2005

Http Headers (304)

Writing about web page http://www.checkupdown.com/status/E304.html

Just reading about browser caching, and the use of the last-modified-date.

It seems there are huge performance gains to be made on static (ish) data by correctly implementing the 304 status code.

{very simplistic overview} Essentially, when content is retrieved from the server, one of the headers (may be) the last-modified-date. When the browser next retrieves this item (on a page refresh) the browser will send back the last-modified-date. If the server decides that the content hasn't changed, then the server will return a 304, informing the browser that their cached version is valid. If the content has changed, the server returns the page.

If the lastModifiedDate of a "page" the server is sending is cheap to calculate then it seems to me that this is a huge optimisation for very little pain.


- No comments Not publicly viewable


Add a comment

You are not allowed to comment on this entry as it has restricted commenting permissions.

May 2005

Mo Tu We Th Fr Sa Su
|  Today  | Jun
                  1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31               

Search this blog

Tags

Galleries

Most recent comments

  • Interesting… While I'm not completely convinced in such microbenchmarks, I'm pretty sure that 1ms … by Alexander Snaps on this entry
  • Hello. I bought the book yesterday. I was trying to find the source code for chapter 11 and chapter … by Suleman on this entry
  • http://woosight.net/account/login?username=demo by live mashup demo on this entry
  • Thanks mate ….. This blog was really helpful. by Maaz Hurzuk on this entry
  • Ty. Not directly helpful for my problem, but pointed me in the right direction. You will also get th… by Mike E. on this entry

Blog archive

Loading…
Not signed in
Sign in

Powered by BlogBuilder
© MMXX