From 4eb4d8da1e68041263627bc54dd613b358e158b5 Mon Sep 17 00:00:00 2001
From: Joe Nelson <cred+github@begriffs.com>
Date: Wed, 26 Nov 2014 21:41:51 -0800
Subject: [PATCH] Removed test for RFC compliance

Who would send Content-Range anyway, that is weird in this context
---
 test/Feature/InsertSpec.hs | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/test/Feature/InsertSpec.hs b/test/Feature/InsertSpec.hs
index df5d56593..a70e565f6 100644
--- a/test/Feature/InsertSpec.hs
+++ b/test/Feature/InsertSpec.hs
@@ -94,13 +94,6 @@ spec = around withApp $ do
 
       context "with a fully-specified primary key" $ do
 
-        context "with Content-Range header" $
-          it "fails as per RFC7231" $
-            request methodPut "/compound_pk?k1=eq.1&k2=eq.2"
-              [("Content-Range", "0-0")]
-              [json| { "k1":1, "k2":2, "extra":3 } |]
-                `shouldRespondWith` 400
-
         context "not specifying every column in the table" $
           it "is rejected for lack of idempotence" $
             request methodPut "/compound_pk?k1=eq.12&k2=eq.42" []