I was looking at the connections being made during a typical gallery request and noticed that some of the files weren't cached. Specifically I found that the files in gs/images and gs/styles are loaded each time the page loads. So I added a web.config file to both of those folders with the following syntax to enable caching:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<staticContent>
<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="3.00:00:00" />
</staticContent>
</system.webServer>
</configuration>

Now when I watch the traffic the image files are only loaded once and each additional requests are cached... Does anyone know if this is going to cause any problems?

Also, to reduce the size of my daily log files I excluded a couple of key files and folders from logging to the IIS logs. Looking at the log files it is obvious that most of the requests for images and thumbnails are done using web handlers, which use GUIDS and not the actual album/image names, making auditing those requests pointless. So for normal auditing of incoming users would mainly be on the default.aspx file.

To accomplish this I added the following sections to the %windir%\system32\inetsrv\config\applicationhost.config file:

<location path="gs/images">
<system.webServer>
<httpLogging dontLog="true" />
</system.webServer>
</location>

<location path="gs/handler">
<system.webServer>
<httpLogging dontLog="true" />
</system.webServer>
</location>

<location path="gs/services">
<system.webServer>
<httpLogging dontLog="true" />
</system.webServer>
</location>

<location path="ComponentArtUploadProgress.axd">
<system.webServer>
<httpLogging dontLog="true" />
</system.webServer>
</location>

Now my logs mostly show connections for the Default.aspx file and little else. Anyone find this useful?

Chris