From 01f6fc75ac92a1655195d0571b4c54dd1c809468 Mon Sep 17 00:00:00 2001 From: Achim Kraus Date: Wed, 16 Nov 2016 15:57:24 +0100 Subject: [PATCH] Test epoch after session resumption. The test shows, its still 1 after resumption. So, is this a bug? If not, I'm wondering, why we need the two variants of isResponse???RelatedToDtlsRequest. Do we want/require to support a reshandshake? Signed-off-by: Achim Kraus --- .../eclipse/californium/scandium/DTLSConnectorTest.java | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/scandium-core/src/test/java/org/eclipse/californium/scandium/DTLSConnectorTest.java b/scandium-core/src/test/java/org/eclipse/californium/scandium/DTLSConnectorTest.java index 9432642ad0..9ef7c9403c 100644 --- a/scandium-core/src/test/java/org/eclipse/californium/scandium/DTLSConnectorTest.java +++ b/scandium-core/src/test/java/org/eclipse/californium/scandium/DTLSConnectorTest.java @@ -654,6 +654,11 @@ public void testConnectorResumesSessionFromExistingConnection() throws Exception // Do a first handshake givenAnEstablishedSession(); byte[] sessionId = establishedServerSession.getSessionIdentifier().getId(); + // save the current epoch + int readEpoch = establishedServerSession.getReadEpoch(); + int writeEpoch = establishedServerSession.getWriteEpoch(); + assertEquals(readEpoch, 1); + assertEquals(writeEpoch, 1); // Force a resume session the next time we send data client.forceResumeSessionFor(serverEndpoint); @@ -674,6 +679,9 @@ public void testConnectorResumesSessionFromExistingConnection() throws Exception connection = clientConnectionStore.get(serverEndpoint); assertArrayEquals(sessionId, connection.getEstablishedSession().getSessionIdentifier().getId()); assertClientIdentity(RawPublicKeyIdentity.class); + // check epochs after resume + assertEquals(readEpoch, connection.getEstablishedSession().getReadEpoch()); + assertEquals(writeEpoch, connection.getEstablishedSession().getWriteEpoch()); } @Test