PUT shouldn't need Idempotence Key

Close #3

Author: javidalpe

README.md

@@ -28,10 +28,10 @@ To perform an idempotent request, provide an additional `Idempotency-Key: <key>`
 
 ### How it works
 
-If the header `Idempotency-Key` is present on the request and the request method is different from GET and DELETE, the middleware stores the response on the cache. Next time you make a request with same idempotency key, the middleware will return the cached response.
+If the header `Idempotency-Key` is present on the request and the request method is different from GET, PUT and DELETE, the middleware stores the response on the cache. Next time you make a request with same idempotency key, the middleware will return the cached response.
 
 How you create unique keys is up to you, but I suggest using V4 UUIDs or another appropriately random string. It'll always send back the same response for requests made with the same key, and keys can't be reused with different request parameters. Keys expire after 24 hours.  
 
 ### License
 
-The Laravel Idempotency is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT)
+The Laravel Idempotency is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT)

src/Idempotency.php

@@ -8,7 +8,7 @@
 class Idempotency
 {
     const IDEMPOTENCY_HEADER = "Idempotency-Key";
-    const EXPIRATION_IN_MINUTES = 60*24;
+    const EXPIRATION_IN_MINUTES = 1440; // 24 hours
 
     /**
      * Handle an incoming request.
@@ -19,7 +19,7 @@ class Idempotency
      */
     public function handle($request, Closure $next)
     {
-        if ($request->method() == 'GET' || $request->method() == 'DELETE') {
+        if ($request->method() == 'GET' || $request->method() == 'PUT' || $request->method() == 'DELETE') {
             return $next($request);
         }