Commit d0606f55 authored by Björn Butzin's avatar Björn Butzin
Browse files

readme corrections

parent bd06717a
......@@ -28,9 +28,9 @@ The HTTP proxy server is started on Port 8080.
As CoAP was designed with proxies in mind, CoAP messages can contain a Proxy-URI option.
The Proxy-URI option is mandatory and should either start with 'http://' or 'coap://' to select the target protocol.
```text
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)
```text
......@@ -51,11 +51,12 @@ 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[PDF](http://www.amd.e-technik.uni-rostock.de/veroeff/2012_Connecting%20the%20Web%20with%20the%20Web%20of%20Things.pdf)
[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)
Proceedings of the IoTech Workshop 2012, Las Vegas, USA, Oktober 2012
```
# Latest Releases
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment