Removed test for RFC compliance

Who would send Content-Range anyway, that is weird in this context
2014-12-06 17:42:21 -08:00
parent f1ecbec543
commit 4eb4d8da1e
1 changed files with 0 additions and 7 deletions
@@ -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" []