On Sat, Jun 6, 2009 at 5:09 AM, djolley<[email protected]> wrote: > >> Most rails websites are fronted by a different webserver that acts as a >> proxy. >> Set that proxy to handle static content and not even pass it to rails. > > OK. That's a good suggestion where there is a front-end proxy. In > this case, there isn't. In any event, I would expect this to be a > very simple problem to solve and I only blamed my own ignorance for > the fact that I was having any difficulty at all. Am I to understand > that this is a problem which does not have a simple solution? > > Thanks for the input. > > ... doug
If you are wanting Rails to stop processing, what should it do? What are you really wanting to achieve? The normal use case is that static files are not served by Rails but in that circumstance, another server would serve them *before* Rails. If you wanted to serve them *after* Rails, then Rails shouldn't stop processing but pass the request on somehow. Andrew Timberlake http://ramblingsonrails.com http://MyMvelope.com - The SIMPLE way to manage your savings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
