Version 0.6.11 (stable)

2012.02.17 Version 0.6.11 (stable)

  • http: allow multiple WebSocket RFC6455 headers (Einar Otto Stangvik)

  • http: allow multiple WWW-Authenticate headers (Ben Noordhuis)

  • windows: support unicode argv and environment variables (Bert Belder)

  • tls: mitigate session renegotiation attacks (Ben Noordhuis)

  • tcp, pipe: don't assert on uv_accept() errors (Ben Noordhuis)

  • tls: Allow establishing secure connection on the existing socket (koichik)

  • dgram: handle close of dgram socket before DNS lookup completes (Seth Fitzsimmons)

  • windows: Support half-duplex pipes (Igor Zinkovsky)

  • build: disable omit-frame-pointer on solaris systems (Dave Pacheco)

  • debugger: fix –debug-brk (Ben Noordhuis)

  • net: fix large file downloads failing (koichik)

  • fs: fix ReadStream failure to read from existing fd (Christopher Jeffrey)

  • net: destroy socket on DNS error (Stefan Rusu)

  • dtrace: add missing translator (Dave Pacheco)

  • unix: don't flush tty on switch to raw mode (Ben Noordhuis)

  • windows: reset brightness when reverting to default text color (Bert Belder)

  • npm: update to 1.1.1

    – Update which, fstream, mkdirp, request, and rimraf
    – Fix #2123 Set path properly for lifecycle scripts on windows
    – Mark the root as seen, so we don't recurse into it. Fixes #1838. (Martin Cooper)

Source Code: http://nodejs.org/dist/v0.6.11/node-v0.6.11.tar.gz

Windows Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.msi

Macintosh Installer: http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg

Website: http://nodejs.org/docs/v0.6.11/

Documentation: http://nodejs.org/docs/v0.6.11/api/

This entry was posted in release. Bookmark the permalink.

5 Responses to Version 0.6.11 (stable)

  1. gitfy says:

    With 0.6.11, the debug-brk option make the process slower tremendously….it uses to be snappy atleast with 0.6.8.

  2. Paulius says:

    The OSX binaries for 0.6.11 are built in 32 rather than 64 bits rendering most, if not all, of the c++ modules unusable (they fail to load). We had to roll back to 0.6.10

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s