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
Capybara
Code Review
CSS
Cucumber
EC2
Eclipse
Ember.js
Firefox
Gettext
Git
grabbing
Hyperestraier
I18n
Javascript
jQuery
JS
Mail
Markdown
Memcached
Model
Mongo
MySql
Nginx
Passenger
Paypal
Plugin
Rails
Rake
Rdoc
Resque
RSpec
Ruby
secruity
Server
Sinatra
Solr
TDD
Test
Textile
Ubuntu
Unix
Varnish
Top Posts & Pages
- A fresh start with Ubuntu Precise Pangolin 12.04
- Ruby Simple Http Post without NET::HTTP Complexity
- current_url for Rails
- The opposite of Rails blank? is present?
- Quick Markdown Preview For Github Readme
- Async Sinatra (Eventmachine) vs Node Performance
- Getting the Caller Method in Ruby
- Compressing a Folder to a Zip Archive with Ruby
- recursive symbolize_keys
- Automated SSH Login with Password and Additional Commands
- Upgrading Ruby from 1.8.6 to 1.8.7 from Source
- one-liner to install nginx with passenger and ssl
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) [...]