coap-coap proxy server about aiocoap HOT 2 CLOSED

the library design should make that relatively simple. rough outline:

• implement a catch-all server; all incoming requests go to the same handler
• strip remote, message-id and token from the request
• figure out whether we want to keep the message type
• send the request yourself (not necessarily through the same context)
• strip remote, message-id and token from the response
• reply with the response

caveats:

• it might be tricky to circumvent the blockwise layer
• the blockwise layer might even bite (afaik it currently matches requests only by remote and path, which would be insufficient here)
• check which unsafe options need to be handled
• should uri-host be stripped?

chances:

• caching proxies
• access control (eg to nodes behind a vpn)
• resource directory

from aiocoap.

the library now ships a coap proxy server, both forward and reverse, and exposes it as a command-line utility.

the api is not stabilized, and some concepts in the background may still change, but it's usable. the "chances" section is not implemented, but should be opened as separate issues on demand.

from aiocoap.