Feature #1042

NDN-WS Proxy for Apps

Added by Alexander Horn almost 8 years ago. Updated almost 7 years ago.

Start date:
Due date:
% Done:


Estimated time:


"I think we need to get into redmine setting up a port 80 proxy on's apache for the NDN-JS communication for the "live" apps hosted on that site. "


Updated by Alexander Horn almost 8 years ago

jeff B suggested this.

yet, does this negate need for nodejs ? how does the websocket get converted to ndn ?


Updated by Jeff Burke almost 8 years ago

This is completely separate from nodejs.

The idea is to simply proxy websocket transport through port 80 on (this is a typical envisioned use for websockets), so that apps deployed on can use port 80 for ndn traffic and work anywhere the website can be accessed.

No ndn-js code changes are needed, only changing the app port and installing/configuring the proxy.


Updated by Alexander Horn almost 8 years ago

well THAT was fun. as it's not part of normal distribution yet. i had to check out apache from source, apply a patch, sacrifice a few oxen, and voila have mod_wsproxy enabled on

however, yet to figure out the configuration.

it seems possible to run both on the same domain, yet it seems to demand an 'absolute path' for the proxy - http:/// or ws://... neither of which is perhaps giving the 'clean' / header-less content that ccnd is likely expecting.

i'll play with this more, but at the moment it still seems to me like there is a step missing / that we need to run node proxy, so we can convert websocket to ccnd face.


Updated by Junxiao Shi about 7 years ago

This Feature can be abandoned because NFD 0.2.0 is deployed on testbed HUBs which has native support of WebSocket faces.


Updated by Alexander Horn almost 7 years ago

  • Status changed from New to Abandoned

Also available in: Atom PDF