Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cf-dev] Handle REQUEST_ENTITY_TOO_LARGE
  • From: Magnus Andersson <mag_andersson@xxxxxxxxxxx>
  • Date: Wed, 24 Jun 2020 10:13:31 +0000
  • Accept-language: sv-SE, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=H0YKrN7VLiQp5G0Rwy46L4SydLNpH3UHlhOsdB14ypw=; b=YARj/G+YCnxpEK76PdK7Q8+36JqPHe+yKxNS780XBEgCpbZChKr0QkVSo8ZDPsK+VIEoQlPz9MWimW9sQEhrNLMWEIkZ3eyGxwvbtuUxK8ZVi/1BRGesec8hFsheu+qLdwW+mCX76eN4VxgBKfH9UbT37tYY6LMLbz2vFCTBO4+VkAGkLZWgGoY+zFARG9Ui6TUgWVRfjQU7kKDZMrYqD8F8jbVaIcXS3KULN5D3XKtaHKKYlI7TZt9t6Z5x8yTXzlqzpsOPkI7lpoA0hv/d78k5oq4jWRYmAdzg1MXutMQgPAJl+ZnZC+m/MqkcPmDA/DT2+u6WcKr6sAMibfAkMw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C5rBuGQMBvznS6P12KHgkhSSDHohOW1vH9P+qcdiJSt9nveEy9xHovBBghzpnSHmWJSSJFmsiXTjyrUUVTbXcYLHednjFdITOAvbsbUqS32jo7e2R/4Gov4/3IuCY6I99MY+jtXakc098qFn/huvRKIvISizg7pqTO3cbXSvHWFTH7xKmNQiMYS6Xk71VyG5+gH8PyPK6p4xdxOm1XAbqbD+Wa7n0+BjrLfg5ffhcRDFvGBd//QX2YM3x12EWRHyna+xxeFDlb8Ji1wvDiPoF2O8X8fDsW+DF0ULSpZ6zDglEQVBKaVdLbdvxnWOAtypPy1XzRUhfhlRwglMgH7I1w==
  • Delivered-to: cf-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/cf-dev>
  • List-help: <mailto:cf-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/cf-dev>, <mailto:cf-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/cf-dev>, <mailto:cf-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHWShAcJcMzrUNQr0Gxp182Vrmp+A==
  • Thread-topic: Handle REQUEST_ENTITY_TOO_LARGE

Hello,

I have a question about block wise transfer in californium. We are running leshan 1.0.0-M8 which is using the californium-core-2.0.0.M1.

We have PREFERRED_BLOCK_SIZE=512.

We have a case where a device responds to POST request with REQUEST_ENTITY_TOO_LARGE. The device only handles 256 bytes, which it responds with (device using wakamaa stack).

The REQUEST_ENTITY_TOO_LARGE response is received by leshan and it boils up to the calling function.

Is there any functionality in californium that automatically handles response REQUEST_ENTITY_TOO_LARGE and starts a new blockwise transfer using the preferred block-size received from device side? (I could not find anything in the code)

If not, how could we handle such a response? Can we from leshan side set the block size for a specific session using the response received from device.

Thanks in advance!

Best regards 
Magnus AnderssoN


Back to the top