Thin::Glazed

This library adds an HTTPS proxy to Thin, which allows you to run your Rails apps that use both HTTP and HTTPS protocols simply within a browser, as well as in your Capybara integration tests, should you so desire.

It was written to keep things consistent – with SSL in development, test and production environments.

This wouldn’t have been possible (or at least, would have been a far larger headache) if it wasn’t for the source and examples of the em-proxy gem.

Installation

Add this line to your application’s Gemfile, in your development and/or test groups:

gem 'thin-glazed'

Using it in development

You can use the glazed server when you fire up your Rails app locally:

./script/rails server thin_glazed

This will provide HTTPS over port 3443 – I use my fork of the bartll-ssl_requirement gem to specify which ports have which protocols, at the end of my config/environments/development.rb file:

SslRequirement.non_ssl_port = 3000
SslRequirement.non_ssl_port = 3443

This ensures redirects from one protocol to the other work accordingly.

If you want to have this as your default development server, add a :require option to the listing in your Gemfile:

gem 'thin-glazed', :require => 'thin/glazed/as_default'

And from there, it’ll just work:

./script/rails server

Using it with tests

Note: this currently has a dependency on my fork of bartll-ssl_requirement. I’d love some suggestions on instructing Rails on what the HTTP and HTTPS ports are without external requirements.

It should just work, if you’re using straight Capybara, or Capybara with Selenium. For Webkit, you’ll want to use :glazed_webkit instead of :webkit for your javascript driver:

Capybara.javascript_driver = :glazed_webkit

Using it in production

Don’t. This isn’t built for production – you’d be far better served with a tool like Pound, or really just letting Nginx or Apache handle it all for you.

Contributing