[riot-notifications] [RIOT-OS/RIOT] gcoap: add simple forward-proxy (#13790)

Cenk Gündoğan notifications at github.com
Thu May 7 16:06:44 CEST 2020


>I wonder if there is a more integrated way to implement this work within gcoap. Conceptually, a forwarding proxy is a specialized listener on the server side. Let's call it a proxy listener. When a message arrives with a Proxy-Uri option, the proxy listener forwards it to the origin server. And when a response arrives from the origin server, the proxy listener forwards it to the requesting client.

@kb2ma @chrysn I have updated the integration to address both your comments: the proxy is now an application and requires almost no modifications to `gcoap`.

The only diff I had to add is [here](https://github.com/RIOT-OS/RIOT/pull/13790/commits/e5a27dbb02d6419f9305e4f067add3ce4dd0d05c). I wish I could also get rid of the modified call to `resource->handler()`, but I could not come up with a cleaner solution to pass the `remote` to the proxy handler. I wonder if passing the memo or the endpoint to the application would be something we want per default?

What's still missing is the implementation of Proxy-Scheme and the consistency check for non-safe-option when copying the options. If we can acknowledge the current way we are moving, then I can add those features (I am aiming to keep the diff as small as possible for review).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/13790#issuecomment-625276878
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200507/b47e03b8/attachment-0001.htm>


More information about the notifications mailing list