First, I apologize for stealing a thread a bit, but this seems to be related to the original issue. This group is a wealth of knowledge so I guess it doesn't hurt to document this here...
In the case of PIE.htc, it only needs a proper content-type and it needs to be referenced in the css (I'm routing /someapp/static to /static): behavior: url(/static/css3pie/PIE.htc); So the proper way of telling web2py what content-type should it use, is to define (in a model): from gluon.contenttype import CONTENT_TYPE CONTENT_TYPE['.htc'] = 'text/x-component' If that does it, it's not a big issue. Just something to document for future projects. I'm barely learning the inner workings of web2py, so I these kind of percepted "bugs" are a good way to progress... Also, just to note - I had good results with using css3pie with IE8 and IE9, so if anyone is in need of CSS3 gradients, box-shadows, rounded corners, etc. on these old fashioned browsers, give it a go.
