This release contains a very evil esi bug that we just found after endless debugging, it is known since 2 weeks (16.11.) and will be fixed in the next release…
Tags
ActiveRecord
Benchmark
Capistrano
Code Review
CSS
Cucumber
ebook
EC2
Eclipse
Firefox
Gettext
Git
Github
grabbing
Hyperestraier
I18n
Javascript
jQuery
JS
Mail
Markdown
Memcached
Model
Mongo
MySql
Nginx
Passenger
Paypal
Plugin
Rails
Rake
Rdoc
RSpec
Ruby
secruity
Server
Sinatra
Solr
TDD
Test
Textile
Threads
Ubuntu
Unix
Varnish
Top Posts & Pages
- Compressing a Folder to a Zip Archive with Ruby
- current_url for Rails
- Automated SSH Login with Password and Additional Commands
- Async Sinatra (Eventmachine) vs Node Performance
- Whats my Coverage? (C0 C1 C2 C3 + Path)
- path_for Rails helper
- Installing redis-server on ubuntu jaunty
- Ruby Parallel Processing made simple
- The opposite of Rails blank? is present?
- Getting Started with Cucumber on Ubuntu
- RSpec: Testing Mail Delivery (simple)
- A fresh start with Ubuntu Oneiric Ocelot 11.10
1 comment
Comments feed for this article
2009-12-11 at 7:34:28
Fixing Varnish restarts after ESI backend dies or timeouts « My Pragmatig life — Michael Grosser
[...] This is for 2.0.4, there are some esi changes/fixes in trunk, so you might want to retest before simply using these settings in a newer version (e.g. sess_workspace is pretty high and will use more ram than necessary) (do not use 2.0.5 with esi) [...]