Great discussion in this thread. Matthew, your analysis and monkey-patch are very impressive! I'm just sorry you guys are stuck reverse-engineering this portion of our stack to get your apps working the way you want - that's definitely bad on us. We're hoping to be able to make heroku_rack open source soon, which should make it a lot easier to get in and tinker with stuff like this.
In the meantime, here's the static asset middleware: http://gist.github.com/480819 One solution here might be to extend can_cache? so that it checks to make sure there isn't already a cache header and thereby avoid clobbering it in the case of a user setting the value. I can't imagine why changing pathnames would affect caching behavior, though. We don't do anything special with paths. Nor has anything in this component changed recently, the last commit on the static asset middleware was in late 2009. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
