@@ -67,6 +67,7 @@ IntelliJ will then automatically import all projects and resolve required Maven
# Tutorial and Examples
The [ws4d-jcoap-handsOn](https://gitlab.amd.e-technik.uni-rostock.de/ws4d/jcoap/tree/master/ws4d-jcoap-handsOn) project provides a guided tutorial to the most common functions of jCoAP.
Example-code can be found in the [ws4d-jcoap-examples](https://gitlab.amd.e-technik.uni-rostock.de/ws4d/jcoap/tree/master/ws4d-jcoap-examples) project.
@@ -31,8 +31,8 @@ The Proxy-URI option is mandatory and should either start with 'http://' or 'coa
Notice that https:// and coaps:// are not supported as security is not implemented yet.
As example the Proxy-URI 'http://127.0.0.1/wanted' will cause the proxy to fetch the 'wanted' resource using HTTP, while the Proxy-URI 'coap://127.0.0.1/wanted' will cause the proxy to fetch the 'wanted' resource using CoAP
The CoAP proxy server is started on port 5683 (CoAP default port)
As example the Proxy-URI 'http://127.0.0.1/wanted' will cause the proxy to fetch the 'wanted' resource using HTTP, while the Proxy-URI 'coap://127.0.0.1/wanted' will cause the proxy to fetch the 'wanted' resource using CoAP.
The CoAP proxy server is started on port 5683 (CoAP default port).
```text
+-----------------------------------------------+
| jCoAP Proxy |
...
...
@@ -51,7 +51,6 @@ Aditionally the proxy starts a second CoAP server on port 5684 offering the '/st
A closer look on the proxy implementation can be foud in:
Christian Lerche, Nico Laum, Frank Golatowski, Christoph Niedermeier, Dirk Timmermann:
[Connecting the Web with the Web of Things: Lessons Learned From Implementing a CoAP-HTTP Proxy](http://www.amd.e-technik.uni-rostock.de/veroeff/2012_Connecting%20the%20Web%20with%20the%20Web%20of%20Things.pdf)