Web2py version is 2.4.6. I did change in stream_file_or_304_or_206 that you proposed, it did not fix the problem.
If my static files are served by web2py, then I understand its wrong for production? Its better to serve them by Apache directly. But how to do this, I`m confused. I thought block *<LocationMatch "^(/[\w_]*/static/.*)">*in httpd.conf was responsible for that. Or I must turn of web2py static file serving somehow? I forgot to tell this, I think this is important details:* *I get only * Content-Type* corrupted headers and only with* .css* files. So far I have not seen other files or headers corrupted. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
