IIS Set Expiration Dates adds the expiration header only to static content

12 Steps To Faster Web Pages With Visual Round Trip Analyzer recommends (among others useful suggestions) to  Set Expiration Dates – follow Using Content Expiration (IIS 6.0), .
Finally the post  IIS Content expiration header and ASP.NET cleared my concerns:
IIS is smart enough to add the expiration header only to static content.
It automatically adds the header to images and css files, without touching
the aspx pages.

 But, like the author of the post, I am also wonder , how does IIS determine what extensions fall under static content? Is
there a way to modify this list?
Related: a few useful advices from Best practices for creating websites in IIS 6.0  
Custom Headers:
Remove the X-Powered-By: ASP.NET header. You really don’t need it unless you want to attach Visual Studio Remote Debugger to your IIS. Otherwise, it’s just sending 21 bytes on every response.
  • Add “From” header and set the server name. I do this on each webserver and specify different names on each box. It’s handy to see from which servers requests are being served. When you are trying to troubleshoot load balancing issues, it comes handy to see if a particular server is sending requests. 
  • Also turn on IIS 6.0 gzip compression.  Note that enabling in IIS 6.0 in the Properties, Service tab is not good enough.
  • More links: