I researched a bug in Apache/wsgiserver and my ISP installed a newer version. The problem went away, so it appears to have been a bug in that layer of the stack.
On Tuesday, March 31, 2015 at 11:40:50 PM UTC-7, Niphlod wrote: > > the file served wrong come from cloudflare though > > > 1. cache-control: > public, max-age=3600 > 2. cf-cache-status: > MISS > 3. cf-ray: > 1d0249f0f33c0e24-MXP > 4. content-type: > http_x_forwarded_proto > 5. date: > Wed, 01 Apr 2015 06:38:02 GMT > 6. expires: > Wed, 01 Apr 2015 07:38:02 GMT > 7. last-modified: > Thu, 26 Mar 2015 22:32:44 GMT > 8. pragma: > cache > 9. server: > cloudflare-nginx > 10. status: > 200 OK > 11. strict-transport-security: > max-age=63072000; includeSubDomains > 12. vary: > Accept-Encoding > 13. version: > HTTP/1.1 > 14. x-content-type-options: > nosniff > 15. x-powered-by: > web2py > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
