secure_headers 0.4.0 → 0.4.1

data/HISTORY.md

@@ -1,10 +1,17 @@
+0.4.1
+======
+
+- Allow strings or ints in the HSTS max-age (@reedloden)
+
 0.4.0
 =======
+
 - Treat each header as it's own before_filter. This allows you to `skip_before_filter :set_X_header, :only => :bad_idea
 - Should be backwards compatible, but it is a change to the API.
 
 0.3.0
 =======
+
 - Greatly reduce the need to use the forward_endpoint attribute. If you are posting from your site to a host that matches TLD+1 (e.g. translate.twitter.com matches twitter.com), use a protocol relative value for report-uri. This will alleviate the need to use forwarding. If your host doesn't match, you still need to use forwarding due to host mismatches for Firefox.
 
 0.2.3

data/README.md

@@ -77,7 +77,7 @@ This gem makes a few assumptions about how you will use some features.  For exam
   }
 end
 
-# and then simply include
+# and then simply include this in application_controller
 ensure_security_headers
 ```
 

data/lib/secure_headers/headers/strict_transport_security.rb

@@ -41,7 +41,7 @@ module SecureHeaders
       if @config.is_a? Hash
         if !@config[:max_age]
           raise STSBuildError.new("No max-age was supplied.")
-        elsif @config[:max_age] !~ /\A\d+\z/
+        elsif @config[:max_age].to_s !~ /\A\d+\z/
           raise STSBuildError.new("max-age must be a number. #{@config[:max_age]} was supplied.")
         end
       else

data/lib/secure_headers/version.rb

@@ -1,3 +1,3 @@
 module SecureHeaders
-  VERSION = "0.4.0"
+  VERSION = "0.4.1"
 end

data/spec/lib/secure_headers/headers/strict_transport_security_spec.rb

@@ -28,6 +28,18 @@ module SecureHeaders
 
       context "with an invalid configuration" do
         context "with a hash argument" do
+          it "should allow string values for max-age" do
+            lambda {
+              StrictTransportSecurity.new(:max_age => '1234')
+            }.should_not raise_error
+          end
+
+          it "should allow integer values for max-age" do
+            lambda {
+              StrictTransportSecurity.new(:max_age => 1234)
+            }.should_not raise_error
+          end
+
           it "raises an exception with an invalid max-age" do
             lambda {
               StrictTransportSecurity.new(:max_age => 'abc123')

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: secure_headers
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.4.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-08 00:00:00.000000000 Z
+date: 2013-04-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: brwsr
@@ -190,7 +190,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
 summary: Add easily configured browser headers to responses including content security