Post #1219794
2025-12-12 03:42 UTC
@osterwood It'd be in an option before the payload -- so the server can, in minimal cases, ingest the request sequentially into a state machine, and can then produce its response. A message might be (sans SLIP escapes): 40 (version 1, confirmable with zero-length token) 01 (GET) 12 34 (message ID), followed by options 31 (1-byte host name) 61 ("a") 84 (4-byte path) 74656d70 ("temp"). So it's GET coap://a/temp. This request has no payload; a POST might, that comes after the headers.
Replies (1)
-
@osterwood@chaos.social 2025-12-12 03:49
@chrysn Got it. I hadn’t fully explored the option details - thanks for the short example