From 32322267dd9e89cb6f0ed07ac7869a57f0eaeb47 Mon Sep 17 00:00:00 2001 From: Victor Shyba Date: Thu, 22 Jun 2017 02:37:37 -0300 Subject: [bug] incoming doesnt accept encryption schemes According to /incoming specification, this parameter doesn't exists. It was added on MX side and brought here on transition. This commit explicitly removes it, leaving a track on history that it got removed during transition. Further work on MX will also remove the "NONE" encryption scheme, which is part of dead code. --- testing/tests/server/test_incoming_resource.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'testing/tests/server/test_incoming_resource.py') diff --git a/testing/tests/server/test_incoming_resource.py b/testing/tests/server/test_incoming_resource.py index e9148b4a..16e1e720 100644 --- a/testing/tests/server/test_incoming_resource.py +++ b/testing/tests/server/test_incoming_resource.py @@ -38,9 +38,9 @@ class IncomingResourceTestCase(unittest.TestCase): def test_save_document(self): formatter = IncomingFormatter() - doc_id, scheme = uuid4().hex, EncryptionSchemes.NONE + doc_id, scheme = uuid4().hex, EncryptionSchemes.PUBKEY content = 'Incoming content' - request = DummyRequest([self.user_uuid, doc_id, scheme]) + request = DummyRequest([self.user_uuid, doc_id]) request.content = BytesIO(content) self.resource.render_PUT(request) -- cgit v1.2.3