I recently purchased and installed a new package for web-based testing so that our Operations group can make sure everyone's skills are sharp, but after installing it on my intranet server, I had a huge jump in the number of 304's in my IIS logs. I just ran some queries on them and turned up that since the beginning of November I've had about 2500 200's logged and over 8600 304's. This isn't the only site running on the server, but almost all of the 304's are from it's URI stem.
Since it's a purchased product and therefore encrypted, I can't make any changes to the code. Does anyone have any clues about something I can change in the configuration to reduce the number of these? I know the 304 code doesn't mean anything is wrong, but it's hard to scan the logs and find problems when they're full of junk.
Since it's a purchased product and therefore encrypted, I can't make any changes to the code. Does anyone have any clues about something I can change in the configuration to reduce the number of these? I know the 304 code doesn't mean anything is wrong, but it's hard to scan the logs and find problems when they're full of junk.
