Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: websockets/ws
base: f5297f7090f6a628832a730187c5b3a06a247f00
Choose a base ref
...
head repository: websockets/ws
compare: e3f0c1720aab640fe78dc578907046fb84422ccd
Choose a head ref
  • 15 commits
  • 22 files changed
  • 3 contributors

Commits on May 25, 2021

  1. Copy the full SHA
    c05d51f View commit details
    Browse the repository at this point in the history

Commits on May 26, 2021

  1. Copy the full SHA
    2f2b3e8 View commit details
    Browse the repository at this point in the history
  2. Copy the full SHA
    d18c677 View commit details
    Browse the repository at this point in the history

Commits on May 27, 2021

  1. [test] Rename certificates and private keys files

    Rename `ca1-cert.pem` to `ca-certificate.pem`, `ca1-key.pem` to
    `ca-key.pem`, `agent1-cert.pem` to `client-certificate.pem`, and
    `agent1-key.pem` to `client-key.pem`.
    lpinca committed May 27, 2021
    Copy the full SHA
    262e45a View commit details
    Browse the repository at this point in the history

Commits on May 28, 2021

  1. [test] Fix nit

    lpinca committed May 28, 2021
    Copy the full SHA
    edff6bb View commit details
    Browse the repository at this point in the history

Commits on May 29, 2021

  1. Copy the full SHA
    7ee3115 View commit details
    Browse the repository at this point in the history

Commits on May 31, 2021

  1. 1
    Copy the full SHA
    03a7078 View commit details
    Browse the repository at this point in the history

Commits on Jun 5, 2021

  1. Copy the full SHA
    05b8ccd View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2021

  1. [fix] Close the connection cleanly when an error occurs

    Instead of destroying the socket, try to close the connection cleanly
    if an error (such as a data framing error) occurs after the opening
    handshake has completed.
    
    Also, to comply with the specification, use the 1006 status code if no
    close frame is received, even if the connection is closed due to an
    error.
    
    Fixes #1898
    lpinca committed Jun 9, 2021
    Copy the full SHA
    8806aa9 View commit details
    Browse the repository at this point in the history
  2. [fix] Don't call ws.terminate() unconditionally in duplex._destroy()

    Call `ws.terminate()` only if `duplex.destroy()` is called directly by
    the user and not indirectly by the listener of the `'error'` event of
    the `WebSocket` object. Calling `ws.terminate()` right after the
    `'error'` event is emitted on the `WebSocket` object, might prevent the
    close frame from being sent to the other peer.
    lpinca committed Jun 9, 2021
    Copy the full SHA
    074e6a8 View commit details
    Browse the repository at this point in the history

Commits on Jun 15, 2021

  1. Copy the full SHA
    c6e3080 View commit details
    Browse the repository at this point in the history
  2. Copy the full SHA
    bb5d44b View commit details
    Browse the repository at this point in the history
  3. [doc] Fix typo

    lpinca committed Jun 15, 2021
    Copy the full SHA
    6eea0d4 View commit details
    Browse the repository at this point in the history
  4. Copy the full SHA
    1d3f4cb View commit details
    Browse the repository at this point in the history

Commits on Jun 16, 2021

  1. [dist] 7.5.0

    lpinca committed Jun 16, 2021
    Copy the full SHA
    e3f0c17 View commit details
    Browse the repository at this point in the history