#27 WebSocket authentication

open
nobody
None
5
2012-09-28
2012-06-17
zachasme
No

When setting username and password with the --rpc-user and --rpc-passwd commandline arguments, I have no idea how to authenticate a WebSocket connection. How does one do this?

Discussion

  • tujikawa

    tujikawa - 2012-06-18

    WebSocket RFC 6455 says that it can use HTTP authorization mechanism in WebSocket handshake.
    WebSocket handshake is in fact HTTP protocol, so it can be done.
    But at the time of this writing, it seems only Firefox supports this.
    I checked Iceweasel 10 (which is Debian counterpart of Firefox 10): when I connected to aria2 via WebSocket, the browser asked me username and password. I entered them and authentication seemed to pass but the WebSocket protocol the browser support is too old and aria2 refused to accept the connection.

    At the moment, Google Chrome does not support HTTP authorization in WebSocket entirely.
    Here is Chrome bug: http://code.google.com/p/chromium/issues/detail?id=123862

     
  • zachasme

    zachasme - 2012-06-18

    I'll just leave the rpc open for now, then. Thanks for the help, and for a great program.

     
  • Ant Bryan

    Ant Bryan - 2012-06-24

    seems to work in Firefox 13.01 and 15 (nightly) with webui-aria2 although I don't know how to tell if its using websocket or just http.

     
  • tujikawa

    tujikawa - 2012-06-26

    Thank you for additional info.
    One way to know whether WebSocket is used or not is inspect aria2's log file.
    If each RPC request comes with HTTP request header, then it is normal HTTP. Otherwise it is WebSocket.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks