no_cache_control 0.0.1 → 1.0.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 32fa5cac25962a36d50c719cef18fedc6d9c03e2
4
- data.tar.gz: 9a90ec98a71607b9f92aadbd2b79acccd7aa82e2
3
+ metadata.gz: 165366993f6be5fa82cb76cc282eb6d6b13de89c
4
+ data.tar.gz: e527f5f591093275d2f56e3d9126b7c8f0c1e3a7
5
5
  SHA512:
6
- metadata.gz: 727f4dc910b5253d691b8617ce8b40deeaa0f9c7f629acb0217b4bcbbebb20b3aba47221b3f908009378ba9c115edb5097ff4a80b55ade811c2441e1a36da283
7
- data.tar.gz: 3e211809f7063a3f55e55de74266f7761f14abdeb97fef2bf7a377a20535bd13d61e682b8f8d9a55036f1edc3a357a23ff14f6903d768f06cdafd999e96ff7f4
6
+ metadata.gz: b6dbe3aeddf4b4eee15621f039d86d248b33103cff1bc23f5e6f94d23aea7ac3c5b7403b6e5dd612479543fceca9252375aa972d03025f573a25da3d487a7fca
7
+ data.tar.gz: 8d27bb1091cf2db7d9a3d0c235aa0d86d481b7770ffaf5343faa106d69b555af67cbc55e517ce6f48ebfa4124ae155664d4f51762d9473a33795f74b2fe3f0a9
data/README.md CHANGED
@@ -5,7 +5,7 @@ bullet-proof, one concern is that Authenticated pages **should
5
5
  not be browser cached**.
6
6
 
7
7
  This is due to fact that even when user is logged out, someone
8
- may sit at his competer and click browser back button and see the
8
+ may sit at users computer and click browser back button and see the
9
9
  restricted data.
10
10
 
11
11
  Gem will set these headers:
@@ -16,17 +16,17 @@ Pragma: no-cache
16
16
  Expires: -1
17
17
  ```
18
18
 
19
- If you are building next-gen Twitter app than this is a bad idea
19
+ If you are building next-gen Twitter app then this is a bad idea
20
20
  because you want to cache as much as possible. But when you're
21
- building comertial Dashboards, payment software, ... than you
22
- must do this.
21
+ building comertial dashboard, payment software, ... then you
22
+ should set those headers.
23
23
 
24
24
  ## Installation
25
25
 
26
26
  Add this line to your application's Gemfile:
27
27
 
28
28
  ```ruby
29
- gem 'no_cache_control', github: equivalent/no_cache_control
29
+ gem 'no_cache_control'
30
30
  ```
31
31
 
32
32
  And then execute:
@@ -39,6 +39,33 @@ Or install it yourself as:
39
39
 
40
40
  ## Usage
41
41
 
42
+ Gem will automaticly automatically append these headers to all your controllers, you don't need to do anything else.
43
+
44
+
45
+ ## How to test if it works
46
+
47
+ No tests for this project as this is deep integration thing. (If anyone want to write a test
48
+ I'm more than happy to merge it in :blush: )
49
+
50
+ The only way how you can test it is to lunch your Rails server and:
51
+
52
+ * open browser, go to the website, and view page headers (like with
53
+ [web developer tools plugin](http://chrispederick.com/work/web-developer/); then
54
+ click in toolbar Information > View Response header)
55
+ * `curl http://0.0.0.0:3000/ -v`
56
+
57
+ ## Tested Versions
58
+
59
+ Gem should work potentionally on any application that uses `ActionController`
60
+ (meaning all Rails versions) but we've tested only these:
61
+
62
+ * works on Rails 4.1.x
63
+ * works on Rails 3.2.x (only under Production env, more info [here](https://github.com/equivalent/no_cache_control/issues/1) and [here](http://stackoverflow.com/questions/26994714/how-to-force-cache-control-to-no-store-in-rails-3-2-20)
64
+
65
+ Please update this README file if you confirm any other
66
+
67
+ ## Todo
68
+
42
69
  * whitelisting of controllers that should be cached
43
70
 
44
71
  ## Contributing
@@ -1,3 +1,3 @@
1
1
  module NoCacheControl
2
- VERSION = "0.0.1"
2
+ VERSION = "1.0.0"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: no_cache_control
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.1
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Tomas Valent
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2014-11-18 00:00:00.000000000 Z
11
+ date: 2014-12-16 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler