rack-ssl-rails 0.0.2

data/.gitignore

@@ -0,0 +1,4 @@
+*.gem
+.bundle
+Gemfile.lock
+pkg/*

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in rack-ssl-rails.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2011 Jesse Storimer
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,22 @@
+Rack::SSL::Rails
+=========
+
+A simple interface to Rack::SSL for Rails.
+
+See http://github.com/josh/rack-ssl
+
+Usage
+-----
+
+Simply add `config.force_ssl = true` to your application configuration to enable the Rack::SSL middleware and force all requests over HTTPS.
+
+Reason
+------
+
+This is a response to the fact that Rack::SSL (and the above config option) are included in core in Rails 3.1. Using SSL in your app is a good idea and Rails should support best practices. But now that Rails depends on this gem my app will depend on it, and load the code, even if the code goes unused. 
+
+There are use cases for not using rack-ssl, with an app that began before Rails 3.1 we already have a solution for forcing SSL in certain areas of the codebase. Besides the fact that I need more fine-grained control over this than a global middleware, I see no reason to switch. Any app that lets users use their own domains will also not be able to use this, at least not without some prior thought.
+
+**IMO this is what the Railties API is for. 'Have it your way'. The Railties API can provide the exact same interface and ease of use, but outside of core rails. This gem could be added to the default Gemfile going forward. That way Rails continues to support best practices without increasing my app's deps unnecessarily.**
+
+https://github.com/rails/rails/commit/2c0c4d754e34b13379dfc53121a970c25fab5dae#commitcomment-383401

data/Rakefile

@@ -0,0 +1,2 @@
+require 'bundler'
+Bundler::GemHelper.install_tasks

data/TODO

@@ -0,0 +1,4 @@
+- Support the HTTP and HTTPS in parallel using method described http://www.simonecarletti.com/blog/2011/05/configuring-rails-3-https-ssl/
+  Overload the config.force_ssl option with symbols
+  config.force_ssl = true
+  config.force_ssl = :https_only

data/lib/rack-ssl-rails.rb

@@ -0,0 +1 @@
+require 'rack/ssl/rails'

data/lib/rack/ssl/rails.rb

@@ -0,0 +1,2 @@
+require 'rack/ssl'
+require 'rack/ssl/rails/railtie'

data/lib/rack/ssl/rails/railtie.rb

@@ -0,0 +1,7 @@
+class Rack::SSL::Railtie < ::Rails::Railtie
+  initializer "middleware" do
+    if config.respond_to?(:force_ssl) && config.force_ssl
+      Rails.application.config.middleware.insert_before ActionDispatch::Static, Rack::SSL
+    end
+  end
+end

data/rack-ssl-rails.gemspec

@@ -0,0 +1,15 @@
+Gem::Specification.new do |s|
+  s.name        = "rack-ssl-rails"
+  s.version     = '0.0.2'
+  s.platform    = Gem::Platform::RUBY
+  s.authors     = ["Jesse Storimer"]
+  s.email       = ["jstorimer@gmail.com"]
+  s.homepage    = ""
+  s.summary     = %q{Provides a railtie for use with rack-ssl.}
+  s.description = %q{Provides a railtie for use with rack-ssl. Includes a handy configuration option that will set up the middleware for you.}
+
+  s.files         = `git ls-files`.split("\n")
+  s.require_paths = ["lib"]
+
+  s.add_runtime_dependency 'rack-ssl'
+end

metadata

@@ -0,0 +1,90 @@
+--- !ruby/object:Gem::Specification 
+name: rack-ssl-rails
+version: !ruby/object:Gem::Version 
+  hash: 27
+  prerelease: 
+  segments: 
+  - 0
+  - 0
+  - 2
+  version: 0.0.2
+platform: ruby
+authors: 
+- Jesse Storimer
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2011-05-17 00:00:00 -04:00
+default_executable: 
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: rack-ssl
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        hash: 3
+        segments: 
+        - 0
+        version: "0"
+  type: :runtime
+  version_requirements: *id001
+description: Provides a railtie for use with rack-ssl. Includes a handy configuration option that will set up the middleware for you.
+email: 
+- jstorimer@gmail.com
+executables: []
+
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- .gitignore
+- Gemfile
+- LICENSE
+- README.md
+- Rakefile
+- TODO
+- lib/rack-ssl-rails.rb
+- lib/rack/ssl/rails.rb
+- lib/rack/ssl/rails/railtie.rb
+- rack-ssl-rails.gemspec
+has_rdoc: true
+homepage: ""
+licenses: []
+
+post_install_message: 
+rdoc_options: []
+
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+requirements: []
+
+rubyforge_project: 
+rubygems_version: 1.6.0
+signing_key: 
+specification_version: 3
+summary: Provides a railtie for use with rack-ssl.
+test_files: []
+