Provided by: websocketd_0.3.1-2_amd64 bug


       websocketd - turns any program that uses STDIN/STDOUT into a WebSocket server.


       websocketd [options] COMMAND [command args]


       websocketd [options] --dir=SOMEDIR


       websocketd  is  a  command  line  tool that will allow any executable program that accepts
       input on stdin and produces output on stdout to be turned into a WebSocket server.

       To learn more about websocketd visit and project WIKI on GitHub!


       A summary of the options supported by websocketd is included below.

           HTTP port to listen on.

           Address to bind to (multiple options allowed). Use square  brackets  to  specify  IPv6
           address. Default: "" (all)

           Restrict (HTTP 403) protocol upgrades if the Origin header does not match to requested
           HTTP Host. Default: false.

           Restrict (HTTP 403) protocol upgrades if the Origin header does not match  to  one  of
           the  host  and port combinations listed. If the port is not specified, any port number
           will match.  Default: "" (allow any origin)

       --ssl --sslcert=FILE --sslkey=FILE
           Listen for HTTPS socket instead of HTTP. All three options must be used or all of them
           should be omitted.

       --passenv VAR[,VAR...]
           Lists environment variables allowed to be passed to executed scripts.

           Perform DNS reverse lookups on remote clients. Default: true

           Allow  all scripts in the local directory to be accessed as WebSockets. If using this,
           option, then the standard program and args options should not be specified.

           Serve static files in this directory over HTTP.

           Serve CGI scripts in this directory over HTTP.

           Print help and exit.

           Print version and exit.

           Print license and exit.

           Enable interactive development console. This enables  you  to  access  the  websocketd
           server  with  a  web-browser  and  use  a  user  interface  to  quickly test WebSocket
           endpoints. For example,  to  test  an  endpoint  at  ws://[host]/foo,  you  can  visit
           http://[host]/foo  in  your  browser.  This  flag  cannot  be used in conjunction with
           --staticdir or --cgidir.

           Log level to use (default access). From most to least verbose: debug,  trace,  access,
           info, error, fatal


         * full documentation at
         * project source at


       The only known condition so far is that certain applications in programming languages that
       enforce implicit STDOUT buffering (Perl, Python, etc.) would be producing unexpected  data
       passing  delays  when  run  under  websocketd.  Such issues could be solved by editing the
       source code of those applications (prohibiting buffering) or modifying  their  environment
       to trick them into autoflush mode (e.g. pseudo-terminal wrapper "unbuffer").

       Active       issues       in      development      are      discussed      on      GitHub:

       Please use that page to share your concerns and  ideas  about  websocketd,  authors  would
       greatly appreciate your help!


       Copyright 2013-2014 Joe Walnes and the websocketd team. All rights reserved.

       BSD license: Run 'websocketd --license' for details.