Hi Trevor,
Keenan is right in that Heroku doesn't support the X-sendfile method:
- http://devcenter.heroku.com/articles/rack-sendfile
The support team initially added this documentation last year after I
submitted an issue regarding problems I was having serving Sass-
generated files from
I'm seeing the following when pushing to Heroku:
Configure Rails 3 to disable x-sendfile
Installing rails3_disable_x_sendfile... done
What is this about? Is there a way I should configure my app to avoid seeing
this message?
--
You received this message because you are subscribed
to Heroku:
Configure Rails 3 to disable x-sendfile
Installing rails3_disable_x_sendfile... done
What is this about? Is there a way I should configure my app to avoid seeing
this message?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post
I have:
config.serve_static_assets = true
...but I don't have anything with:
config.action_dispatch.x_sendfile_header
...at all. Perhaps you are doing something unnecessarily in my case? You can
view my app teamlab yourself on Heroku if you like. I can file a support
ticket if necessarily.
Hello Trevor,
Web servers (e.g.: Apache) is tuned for serving up static files.
Ruby (e.g.: mongrel) is not as efficient at serving up static files.
But sometimes, your ruby code generates a file that needs to be streamed. Or it
uses logic to determine the name of an existing file that needs to
On Monday, March 21, 2011 12:06:35 PM UTC, Keenan wrote:
So you need to tell rails to not use the handy X-sendfile header and stream
the file through.
How this affects Heroku?
The web server is running on a different machine than the dynos. So
X-sendfile doesn't work.
So they modify
