• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 432
  • Last Modified:

"HTTP Headers" "Enable Content Expiration" option

I have IIS7 windows 2008 64bit RC2
I have half of the events in the IIS logfiles as 304 error code.

If i set it to expire immediately ; the following occurs.

the user signs into the web app, then runs a report to be processed and the report when finished is stored on the NAS drive, and when they click on a link that point to the file to open , it comes up blank.  so is there a good settings that keeps the 304 from taking up half of the logfile entries but i cannot used immediately because the reports (regardless of format) come up blank

any thoughts or suggestions will be most grateful
thank you
0
mphillip85
Asked:
mphillip85
  • 3
  • 3
1 Solution
 
Dave BaldwinFixer of ProblemsCommented:
'304' is not an error code, it "Indicates the resource has not been modified since last requested.".  That is actually a good sign because it means that browser caching is working properly and reducing the amount of bandwidth required.  Read more about it here:

http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection
0
 
mphillip85Author Commented:
so if you logfile is 540,000 lines and you have 253,000 lines thats ok.

would it be ok just to expires set to 1 day so we dont have as many lines of 304?

my goal is to safely get the highest count of 200 code as possible, i have a whole slew of other errors to contend with, so i am just trying to widdle down the lines of non 200's

thank you
0
 
mphillip85Author Commented:
on the pc i have " check for newer versions of pages" automatically
is this what is triggering the 304?
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
Dave BaldwinFixer of ProblemsCommented:
304 is Not an error.  It is the browser on the clients checking for newer versions that causes the 304's.  A 304 is equivalent to a 200 and you really shouldn't be trying to reduce them.  A 304 tells the browser that the content has not changed and that they can use the version in their cache instead of downloading a new copy of the page.  It reduces the amount of bandwidth required.  253,000 lines out of 540,000 is just fine.  That tells you that half of the time, your clients are requesting pages that they have seen before.
0
 
mphillip85Author Commented:
he was very thorough in his explanation, which is very curtious and i am grateful for the great feedback that was given.
0
 
Dave BaldwinFixer of ProblemsCommented:
Glad to help.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now