20T08:31:29+00:00 heroku[router]: Error H13 (Connection closed
> > > without response) -> GET mysite.heroku.com/assets/application-
> > > b1637fec79c8bbd5d3a18e84f3da878f.css dyno=web.1 queue=0 wait=0ms
> > > service=0ms bytes=0
> > > 2011-05-20T01
t response) -> GET mysite.heroku.com/assets/application-
> > b1637fec79c8bbd5d3a18e84f3da878f.css dyno=web.1 queue=0 wait=0ms
> > service=0ms bytes=0
> > 2011-05-20T01:31:29-07:00 heroku[nginx]: GET / HTTP/1.1 |
> > 72.229.127.215 | 1480 | http | 200
>
>
7.215 | 1480 | http | 200
>
> both edge and beta1 have the same results:
>
> Gemfile:
>
> source 'http://rubygems.org'
>
> #gem 'rails', '3.1.0.beta1'
> gem 'rails', git: 'git://github.com/rails/rails.git'
>
> gem
x27;, '3.1.0.beta1'
gem 'rails', git: 'git://github.com/rails/rails.git'
gem 'pg'
gem 'therubyracer-heroku', '0.8.1.pre3'
# Asset template engines
gem 'sass'
gem 'coffee-script'
gem 'uglifier'
gem 'jquery-rails
Hello there,
I was curious and tried if I can use the new assets pipeline that
comes with Rails 3.1 beta (sprockets). From time to time I am getting
a 503 for requests of those merged application.js/.css files, an
example from my log:
2011-05-11T12:26:10+00:00 app[web.1]: cache: [GET /assets/
app