This brings back memories. I believe I may have had a similar problem recently. Apache & mod_wsgi, web2py 1.99.2.
I wanted to use css3pie to overcome IE8 and IE9 lack of CSS3 support. IE8 is easy going, but IE9 strictly demands a correct file-type for the PIE.htc behaviour file in order to use it. So I did all that, had the correct content-type settings in Apache's configuration, got IE8 going just fine. But IE9 was lying dead in the water. Hm. I tried all possible solutions, even had Apache force content-type for an entire directory (didn't realize Apache has that many content-type enforcing possibilities), had css trigger different IE9 compatibility modes, tried god knows what to nudge IE9 into accepting PIE.htc. Nothing! And than it finally struck me... My PIE.htc still opens as text in browser. Wait a minute... It shouldn't do that. It should download. Once I moved PIE.htc file out of web2py entirely (it was in static/something/something), Apache content type was taken into account and it started working right away. This was one of *those* head scrathing bugs that make me chuckle afterwards and which I usually remember for a while. :) If static files are indeed meant to be served before hitting the app code, then it must be a bug somewhere. Apache content-type doesn't seem to apply. Or does using web2py routes cause this? I had /someapp/static routed to /static. Anyway... AddType text/x-component .htc
