source: trip-planner-front/node_modules/websocket-driver/CHANGELOG.md@ eed0bf8

Last change on this file since eed0bf8 was 6a3a178, checked in by Ema <ema_spirova@…>, 3 years ago

initial commit

  • Property mode set to 100644
File size: 4.0 KB
Line 
1### 0.7.4 / 2020-05-22
2
3- Avoid crashing if `process.version` does not contain any digits
4- Emit `ping` and `pong` events from the `Server` driver
5- Require http-parser-js >=0.5.1 which fixes the bug we addressed in 0.7.3
6
7### 0.7.3 / 2019-06-13
8
9- Cap version of http-parser-js below 0.4.11, which introduced a bug that
10 prevents us from handling messages that are part of the same input buffer as
11 the handshake response if chunked encoding is specified
12
13### 0.7.2 / 2019-06-13
14
15(This version was pulled due to an error when publishing)
16
17### 0.7.1 / 2019-06-10
18
19- Catch any exceptions produced while generating a handshake response and send a
20 `400 Bad Request` response to the client
21- Pick the RFC-6455 protocol version if the request contains any of the headers
22 used by that version
23- Use the `Buffer.alloc()` and `Buffer.from()` functions instead of the unsafe
24 `Buffer()` constructor
25- Handle errors encountered while handling malformed draft-76 requests
26- Change license from MIT to Apache 2.0
27
28### 0.7.0 / 2017-09-11
29
30- Add `ping` and `pong` to the set of events users can listen to
31- Replace the bindings to Node's HTTP parser with `http-parser-js`
32
33### 0.6.5 / 2016-05-20
34
35- Don't mutate buffers passed in by the application when masking
36
37### 0.6.4 / 2016-01-07
38
39- If a number is given as input for a frame payload, send it as a string
40
41### 0.6.3 / 2015-11-06
42
43- Reject draft-76 handshakes if their Sec-WebSocket-Key headers are invalid
44- Throw a more helpful error if a client is created with an invalid URL
45
46### 0.6.2 / 2015-07-18
47
48- When the peer sends a close frame with no error code, emit 1000
49
50### 0.6.1 / 2015-07-13
51
52- Use the `buffer.{read,write}UInt{16,32}BE` methods for reading/writing numbers
53 to buffers rather than including duplicate logic for this
54
55### 0.6.0 / 2015-07-08
56
57- Allow the parser to recover cleanly if event listeners raise an error
58- Add a `pong` method for sending unsolicited pong frames
59
60### 0.5.4 / 2015-03-29
61
62- Don't emit extra close frames if we receive a close frame after we already
63 sent one
64- Fail the connection when the driver receives an invalid
65 `Sec-WebSocket-Extensions` header
66
67### 0.5.3 / 2015-02-22
68
69- Don't treat incoming data as WebSocket frames if a client driver is closed
70 before receiving the server handshake
71
72### 0.5.2 / 2015-02-19
73
74- Fix compatibility with the HTTP parser on io.js
75- Use `websocket-extensions` to make sure messages and close frames are kept in
76 order
77- Don't emit multiple `error` events
78
79### 0.5.1 / 2014-12-18
80
81- Don't allow drivers to be created with unrecognized options
82
83### 0.5.0 / 2014-12-13
84
85- Support protocol extensions via the websocket-extensions module
86
87### 0.4.0 / 2014-11-08
88
89- Support connection via HTTP proxies using `CONNECT`
90
91### 0.3.6 / 2014-10-04
92
93- It is now possible to call `close()` before `start()` and close the driver
94
95### 0.3.5 / 2014-07-06
96
97- Don't hold references to frame buffers after a message has been emitted
98- Make sure that `protocol` and `version` are exposed properly by the TCP driver
99
100### 0.3.4 / 2014-05-08
101
102- Don't hold memory-leaking references to I/O buffers after they have been
103 parsed
104
105### 0.3.3 / 2014-04-24
106
107- Correct the draft-76 status line reason phrase
108
109### 0.3.2 / 2013-12-29
110
111- Expand `maxLength` to cover sequences of continuation frames and
112 `draft-{75,76}`
113- Decrease default maximum frame buffer size to 64MB
114- Stop parsing when the protocol enters a failure mode, to save CPU cycles
115
116### 0.3.1 / 2013-12-03
117
118- Add a `maxLength` option to limit allowed frame size
119- Don't pre-allocate a message buffer until the whole frame has arrived
120- Fix compatibility with Node v0.11 `HTTPParser`
121
122### 0.3.0 / 2013-09-09
123
124- Support client URLs with Basic Auth credentials
125
126### 0.2.2 / 2013-07-05
127
128- No functional changes, just updates to package.json
129
130### 0.2.1 / 2013-05-17
131
132- Export the isSecureRequest() method since faye-websocket relies on it
133- Queue sent messages in the client's initial state
134
135### 0.2.0 / 2013-05-12
136
137- Add API for setting and reading headers
138- Add Driver.server() method for getting a driver for TCP servers
139
140### 0.1.0 / 2013-05-04
141
142- First stable release
Note: See TracBrowser for help on using the repository browser.