I looked at the compression code and the excluded paths logic is pretty straightforward.
At runtime, the requested URL is parsed to a relative path from the root of your web site, so for example, if the Raw URL is something like this...
|
http://www.gooddogs.com/Dotnetnuke/DesktopModules/Repository/MakeThumbnail.aspx
|
then after parsing, the 'real path' will be
|
DesktopModules/Repository/MakeThumbnail.aspx
|
Then a call to the IsExcludedPath(string realPath) is made to determine whether or not to exclude the output from that page from compression. If the function returns TRUE, then the page output will not be compressed.
|
if(settings.IsExcludedPath(realPath))
{
// skip if the file path excludes compression
return;
}
|
The IsExcludedPath function is a simple one
|
/// <summary>
/// Looks for a given path in the list of paths excluded from compression
/// </summary>
/// <param name="relUrl">the relative url to check</param>
/// <returns>true if excluded, false if not</returns>
public bool IsExcludedPath(string relUrl) {
return _excludedPaths.Contains(relUrl.ToLower());
}
|
As you can see, the function simply does a check to see if the real path that is passed in is in the collection of excluded paths ( converting them to lower case to avoid case sensitive issues ). So there really isn't any 'syntax' or regex type rules for specifying excluded paths, just add a relative path from the DotNetNuke root folder to the page you wish to exclude.
Hope that helps.