[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] Handle REQUEST_ENTITY_TOO_LARGE
|
Hi,
I think, this is related to
https://github.com/eclipse/californium/issues/395
from summer 2017.
Unfortunately, no volunteer was found to implement it ;-(.
So, no Californium doesn't have that function.
Mit freundlichen Grüßen / Best regards
Achim Kraus
Bosch IoT Hub - Product Area IoT Platform (IOC/PAP-HU)
Bosch.IO GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY | www.bosch.io
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne Reckling
-----Ursprüngliche Nachricht-----
Von: cf-dev-bounces@xxxxxxxxxxx <cf-dev-bounces@xxxxxxxxxxx> Im Auftrag von Magnus Andersson
Gesendet: Mittwoch, 24. Juni 2020 12:14
An: cf-dev@xxxxxxxxxxx
Betreff: [cf-dev] 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
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cf-dev
