7 1) MAJOR (Windows-only) fix assert firing
9 2) MAJOR http:/1.1 connections handled by lws_return_http_status() did not
10 get sent a content-length resulting in the link hanging until the peer closed
11 it. attack.sh updated to add a test for this.
13 3) MINOR An error about hdr struct in _lws_ws_related is corrected, it's not
14 known to affect anything until after it was fixed
16 4) MINOR During the close shutdown wait state introduced at v1.7, if something
17 requests callback on writeable for the socket it will busywait until the
20 5) MAJOR Although the test server has done it for a few versions already, it
21 is now required for the user code to explicitly call
23 if (lws_http_transaction_completed(wsi))
26 when it finishes replying to a transaction in http. Previously the library
27 did it for you, but that disallowed large, long transfers with multiple
28 trips around the event loop (and cgi...).
30 6) MAJOR connections on ah waiting list that closed did not get removed from
33 7) MAJOR since we added the ability to hold an ah across http keepalive
34 transactions where more headers had already arrived, we broke the ability
35 to tell if more headers had arrived. Result was if the browser didn't
36 close the keepalive, we retained ah for the lifetime of the keepalive,
39 8) MAJOR windows-only-POLLHUP was not coming
41 9) Client should not send ext hdr if no exts
46 1) MINOR test-server gained some new switches
48 -C <file> use external SSL cert file
49 -K <file> use external SSL key file
50 -A <file> use external SSL CA cert file
52 -u <uid> set effective uid
53 -g <gid> set effective gid
55 together you can use them like this to have the test-server work with the
56 usual purchased SSL certs from an official CA.
58 --ssl -C your.crt -K your.key -A your.cer -u 99 -g 99
60 2) MINOR the OpenSSL magic to setup ECDH cipher usage is implemented in the
61 library, and the ciphers restricted to use ECDH only.
62 Using this, the lws test server can score an A at SSLLABS test
64 3) MINOR STS (SSL always) header is added to the test server if you use --ssl. With
65 that, we score A+ at SSLLABS test
67 4) MINOR daemonize function (disabled at cmake by default) is updated to work
70 5) MINOR example systemd .service file now provided for test server
71 (not installed by default)
73 6) test server html is updated with tabs and a new live server monitoring
74 feature. Input sanitization added to the js.
76 7) client connections attempted when no ah is free no longer fail, they are
77 just deferred until an ah becomes available.
79 8) The test client pays attention to if you give it an http:/ or https://
80 protocol string to its argument in URL format. If so, it stays in http[s]
81 client mode and doesn't upgrade to ws[s], allowing you to do generic http client
82 operations. Receiving transfer-encoding: chunked is supported.
84 9) The test server has a new URI path http://localhost:7681/proxytest
85 If you visit here, a client connection to http://example.com:80 is spawned,
86 and the results piped on to your original connection.
92 1) MINOR APIBREAK There's a new member in struct lws_context_creation_info, ecdh_curve,
93 which lets you set the name of the ECDH curve OpenSSL should use. By
94 default (if you leave ecdh_curve NULL) it will use "prime256v1"
96 2) MINOR NEWAPI It was already possible to adopt a foreign socket that had not
97 been read from using lws_adopt_socket() since v1.7. Now you can adopt a
98 partially-used socket if you don't need SSL, by passing it what you read
99 so it can drain that before reading from the socket.
101 LWS_VISIBLE LWS_EXTERN struct lws *
102 lws_adopt_socket_readbuf(struct lws_context *context, lws_sockfd_type accept_fd,
103 const char *readbuf, size_t len);
105 3) MINOR NEWAPI CGI type "network io" subprocess execution is now possible from
108 LWS_VISIBLE LWS_EXTERN int
109 lws_cgi(struct lws *wsi, char * const *exec_array, int timeout_secs);
111 LWS_VISIBLE LWS_EXTERN int
112 lws_cgi_kill(struct lws *wsi);
114 To use it, you must first set the cmake option
116 $ cmake .. -DLWS_WITH_CGI=1
118 See test-server-http.c and test server path
120 http://localhost:7681/cgitest
122 stdin gets http body, you can test it with wget
124 $ echo hello > hello.txt
125 $ wget http://localhost:7681/cgitest --post-file=hello.txt -O- --quiet
129 4) There is a helper api for forming logging timestamps
132 lwsl_timestamp(int level, char *p, int len)
134 this generates this kind of timestamp for use as logging preamble
136 lwsts[13116]: [2016/01/25 14:52:52:8386] NOTICE: Initial logging level 7
138 5) struct lws_client_connect_info has a new member
142 If it's NULL, then everything happens as before, lws_client_connect_via_info()
143 makes a ws or wss connection to the address given.
145 If you set method to a valid http method like "GET", though, then this method
146 is used and the connection remains in http[s], it's not upgraded to ws[s].
148 So with this, you can perform http[s] client operations as well as ws[s] ones.
150 There are 4 new related callbacks
152 LWS_CALLBACK_ESTABLISHED_CLIENT_HTTP = 44,
153 LWS_CALLBACK_CLOSED_CLIENT_HTTP = 45,
154 LWS_CALLBACK_RECEIVE_CLIENT_HTTP = 46,
155 LWS_CALLBACK_COMPLETED_CLIENT_HTTP = 47,
157 6) struct lws_client_connect_info has a new member
159 const char *parent_wsi
161 if non-NULL, the client wsi is set to be a child of parent_wsi. This ensures
162 if parent_wsi closes, then the client child is closed just before.
164 7) If you're using SSL, there's a new context creation-time option flag
165 LWS_SERVER_OPTION_REDIRECT_HTTP_TO_HTTPS. If you give this, non-ssl
166 connections to the server listen port are accepted and receive a 301
167 redirect to / on the same host and port using https://
176 1) There is now a "permessage-deflate" / RFC7692 implementation. It's very
177 similar to "deflate-frame" we have offered for a long while; deflate-frame is
178 now provided as an alias of permessage-deflate.
180 The main differences are that the new permessage-deflate implementation:
182 - properly performs streaming respecting input and output buffer limits. The
183 old deflate-frame implementation could only work on complete deflate input
184 and produce complete inflate output for each frame. The new implementation
185 only mallocs buffers at initialization.
187 - goes around the event loop after each input package is processed allowing
188 interleaved output processing. The RX flow control api can be used to
189 force compressed input processing to match the rate of compressed output
190 processing (test--echo shows an example of how to do this).
192 - when being "deflate-frame" for compatibility he uses the same default zlib
193 settings as the old "deflate-frame", but instead of exponentially increasing
194 malloc allocations until the whole output will fit, he observes the default
195 input and output chunking buffer sizes of "permessage-deflate", that's
196 1024 in and 1024 out at a time.
198 2) deflate-stream has been disabled for many versions (for over a year) and is
199 now removed. Browsers are now standardizing on "permessage-deflate" / RFC7692
201 3) struct lws_extension is simplified, and lws extensions now have a public
202 api (their callback) for use in user code to compose extensions and options
203 the user code wants. lws_get_internal_exts() is deprecated but kept around
204 as a NOP. The changes allow one extension implementation to go by different
205 names and allows the user client code to control option offers per-ext.
207 The test client and server are updated to use the new way. If you use
208 the old way it should still work, but extensions will be disabled until you
211 Extensions are now responsible for allocating and per-instance private struct
212 at instance construction time and freeing it when the instance is destroyed.
213 Not needing to know the size means the extension's struct can be opaque
220 1) The info struct gained three new members
222 - max_http_header_data: 0 for default (1024) or set the maximum amount of known
223 http header payload that lws can deal with. Payload in unknown http
224 headers is dropped silently. If for some reason you need to send huge
225 cookies or other HTTP-level headers, you can now increase this at context-
228 - max_http_header_pool: 0 for default (16) or set the maximum amount of http
229 headers that can be tracked by lws in this context. For the server, if
230 the header pool is completely in use then accepts on the listen socket
231 are disabled until one becomes free. For the client, if you simultaneously
232 have pending connects for more than this number of client connections,
233 additional connects will fail until some of the pending connections timeout
236 - timeout_secs: 0 for default (currently 20s), or set the library's
237 network activity timeout to the given number of seconds
239 HTTP header processing in lws only exists until just after the first main
240 callback after the HTTP handshake... for ws connections that is ESTABLISHED and
241 for HTTP connections the HTTP callback.
243 So these settings are not related to the maximum number of simultaneous
244 connections, but the number of HTTP handshakes that may be expected or ongoing,
245 or have just completed, at one time. The reason it's useful is it changes the
246 memory allocation for header processing to be one-time at context creation
247 instead of every time there is a new connection, and gives you control over
250 Setting max_http_header_pool to 1 is fine it will just queue incoming
251 connections before the accept as necessary, you can still have as many
252 simultaneous post-header connections as you like. Since the http header
253 processing is completed and the allocation released after ESTABLISHED or the
254 HTTP callback, even with a pool of 1 many connections can be handled rapidly.
256 2) There is a new callback that allows the user code to get acccess to the
257 optional close code + aux data that may have been sent by the peer.
259 LWS_CALLBACK_WS_PEER_INITIATED_CLOSE:
260 The peer has sent an unsolicited Close WS packet. @in and
261 @len are the optional close code (first 2 bytes, network
262 order) and the optional additional information which is not
263 defined in the standard, and may be a string or non-human-
265 If you return 0 lws will echo the close and then close the
266 connection. If you return nonzero lws will just close the
269 As usual not handling it does the right thing, if you're not interested in it
272 The test server has "open and close" testing buttons at the bottom, if you
273 open and close that connection, on close it will send a close code 3000 decimal
274 and the string "Bye!" as the aux data.
276 The test server dumb-increment callback handles this callback reason and prints
278 lwsts[15714]: LWS_CALLBACK_WS_PEER_INITIATED_CLOSE: len 6
279 lwsts[15714]: 0: 0x0B
280 lwsts[15714]: 1: 0xB8
281 lwsts[15714]: 2: 0x42
282 lwsts[15714]: 3: 0x79
283 lwsts[15714]: 4: 0x65
284 lwsts[15714]: 5: 0x21
286 3) There is a new API to allow the user code to control the content of the
287 close frame sent when about to return nonzero from the user callback to
288 indicate the connection should close.
291 * lws_close_reason - Set reason and aux data to send with Close packet
292 * If you are going to return nonzero from the callback
293 * requesting the connection to close, you can optionally
294 * call this to set the reason the peer will be told if
297 * @wsi: The websocket connection to set the close reason on
298 * @status: A valid close status from websocket standard
299 * @buf: NULL or buffer containing up to 124 bytes of auxiliary data
300 * @len: Length of data in @buf to send
302 LWS_VISIBLE LWS_EXTERN void
303 lws_close_reason(struct lws *wsi, enum lws_close_status status,
304 unsigned char *buf, size_t len);
306 An extra button is added to the "open and close" test server page that requests
307 that the test server close the connection from his end.
309 The test server code will do so by
311 lws_close_reason(wsi, LWS_CLOSE_STATUS_GOINGAWAY,
312 (unsigned char *)"seeya", 5);
315 The browser shows the close code and reason he received
317 websocket connection CLOSED, code: 1001, reason: seeya
319 4) There's a new context creation time option flag
321 LWS_SERVER_OPTION_VALIDATE_UTF8
323 if you set it in info->options, then TEXT and CLOSE frames will get checked to
324 confirm that they contain valid UTF-8. If they don't, the connection will get
327 5) ECDH Certs are now supported. Enable the CMake option
329 cmake .. -DLWS_SSL_SERVER_WITH_ECDH_CERT=1
331 **and** the info->options flag
333 LWS_SERVER_OPTION_SSL_ECDH
335 to build in support and select it at runtime.
337 6) There's a new api lws_parse_uri() that simplifies chopping up
338 https://xxx:yyy/zzz uris into parts nicely. The test client now uses this
339 to allow proper uris as well as the old address style.
341 7) SMP support is integrated into LWS without any internal threading. It's
342 very simple to use, libwebsockets-test-server-pthread shows how to do it,
343 use -j <n> argument there to control the number of service threads up to 32.
345 Two new members are added to the info struct
347 unsigned int count_threads;
348 unsigned int fd_limit_per_thread;
350 leave them at the default 0 to get the normal singlethreaded service loop.
352 Set count_threads to n to tell lws you will have n simultaneous service threads
353 operating on the context.
355 There is still a single listen socket on one port, no matter how many
358 When a connection is made, it is accepted by the service thread with the least
359 connections active to perform load balancing.
361 The user code is responsible for spawning n threads running the service loop
362 associated to a specific tsi (Thread Service Index, 0 .. n - 1). See
363 the libwebsockets-test-server-pthread for how to do.
365 If you leave fd_limit_per_thread at 0, then the process limit of fds is shared
366 between the service threads; if you process was allowed 1024 fds overall then
367 each thread is limited to 1024 / n.
369 You can set fd_limit_per_thread to a nonzero number to control this manually, eg
370 the overall supported fd limit is less than the process allowance.
372 You can control the context basic data allocation for multithreading from Cmake
373 using -DLWS_MAX_SMP=, if not given it's set to 32. The serv_buf allocation
374 for the threads (currently 4096) is made at runtime only for active threads.
376 Because lws will limit the requested number of actual threads supported
377 according to LWS_MAX_SMP, there is an api lws_get_count_threads(context) to
378 discover how many threads were actually allowed when the context was created.
380 It's required to implement locking in the user code in the same way that
381 libwebsockets-test-server-pthread does it, for the FD locking callbacks.
383 If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the
384 library. If more than 1, a small amount of pthread mutex code is built into
389 LWS_VISIBLE struct lws *
390 lws_adopt_socket(struct lws_context *context, lws_sockfd_type accept_fd)
392 allows foreign sockets accepted by non-lws code to be adopted by lws as if they
393 had just been accepted by lws' own listen socket.
395 9) X-Real-IP: header has been added as WSI_TOKEN_HTTP_X_REAL_IP
397 10) Libuv support is added, there are new related user apis
399 typedef void (lws_uv_signal_cb_t)(uv_loop_t *l, uv_signal_t *w, int revents);
401 LWS_VISIBLE LWS_EXTERN int
402 lws_uv_sigint_cfg(struct lws_context *context, int use_uv_sigint,
403 lws_uv_signal_cb_t *cb);
405 LWS_VISIBLE LWS_EXTERN int
406 lws_uv_initloop(struct lws_context *context, uv_loop_t *loop, int tsi);
409 lws_uv_sigint_cb(uv_loop_t *loop, uv_signal_t *watcher, int revents);
419 1) LWS_SEND_BUFFER_POST_PADDING is now 0 and deprecated. You can remove it; if
420 you still use it, obviously it does nothing. Old binary code with nonzero
421 LWS_SEND_BUFFER_POST_PADDING is perfectly compatible, the old code just
422 allocated a buffer bigger than the library is going to use.
424 The example apps no longer use LWS_SEND_BUFFER_POST_PADDING.
426 The only path who made use of it was sending with LWS_WRITE_CLOSE --->
428 2) Because of lws_close_reason() formalizing handling close frames,
429 LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send
430 close frames...close frame content should be managed using lws_close_reason()
433 3) We check for invalid CLOSE codes and complain about protocol violation in
434 our close code. But it changes little since we were in the middle of closing
437 4) zero-length RX frames and zero length TX frames are now allowed.
439 5) Pings and close used to be limited to 124 bytes, the correct limit is 125
440 so that is now also allowed.
442 6) LWS_PRE is provided as a synonym for LWS_SEND_BUFFER_PRE_PADDING, either is
445 7) There's generic support for RFC7462 style extension options built into the
446 library now. As a consequence, a field "options" is added to lws_extension.
447 It can be NULL if there are no options on the extension. Extension internal
448 info is part of the public abi because extensions may be implemented outside
451 8) WSI_TOKEN_PROXY enum was accidentally defined to collide with another token
452 of value 73. That's now corrected and WSI_TOKEN_PROXY moved to his own place at
455 9) With the addition of libuv support, libev is not the only event loop
456 library in town and his api names must be elaborated with _ev_
458 Callback typedef: lws_signal_cb ---> lws_ev_signal_cb_t
459 lws_sigint_cfg --> lws_ev_sigint_cfg
460 lws_initloop --> lws_ev_initloop
461 lws_sigint_cb --> lws_ev_sigint_cb
463 10) Libev support is made compatible with multithreaded service,
464 lws_ev_initloop (was lws_initloop) gets an extra argument for the
465 thread service index (use 0 if you will just have 1 service thread).
467 LWS_VISIBLE LWS_EXTERN int
468 lws_ev_initloop(struct lws_context *context, ev_loop_t *loop, int tsi);
471 v1.6.0-chrome48-firefox42
472 =======================
474 Major API improvements
475 ----------------------
477 v1.6.0 has many cleanups and improvements in the API. Although at first it
478 looks pretty drastic, user code will only need four actions to update it.
480 - Do the three search/replaces in your user code, /libwebsocket_/lws_/,
481 /libwebsockets_/lws_/, and /struct\ libwebsocket/struct\ lws/
483 - Remove the context parameter from your user callbacks
485 - Remove context as the first parameter from the "Eleven APIS" listed in the
486 User Api Changes section
488 - Add lws_get_context(wsi) as the first parameter on the "Three APIS" listed
489 in the User Api Changes section, and anywhere else you still need context
491 That's it... generally only a handful of the 14 affected APIs are actually in
492 use in your user code and you can find them quickest by compiling and visiting
493 the errors each in turn. And the end results are much cleaner, more
494 predictable and maintainable.
500 1) lws now exposes his internal platform file abstraction in a way that can be
501 both used by user code to make it platform-agnostic, and be overridden or
502 subclassed by user code. This allows things like handling the URI "directory
503 space" as a virtual filesystem that may or may not be backed by a regular
504 filesystem. One example use is serving files from inside large compressed
505 archive storage without having to unpack anything except the file being
508 The test server shows how to use it, basically the platform-specific part of
509 lws prepares a file operations structure that lives in the lws context.
511 Helpers are provided to also leverage these platform-independent file handling
514 static inline lws_filefd_type
515 lws_plat_file_open(struct lws *wsi, const char *filename,
516 unsigned long *filelen, int flags)
518 lws_plat_file_close(struct lws *wsi, lws_filefd_type fd)
520 static inline unsigned long
521 lws_plat_file_seek_cur(struct lws *wsi, lws_filefd_type fd, long offset)
524 lws_plat_file_read(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
525 unsigned char *buf, unsigned long len)
528 lws_plat_file_write(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
529 unsigned char *buf, unsigned long len)
531 The user code can also override or subclass the file operations, to either
532 wrap or replace them. An example is shown in test server.
534 A wsi can be associated with the file activity, allowing per-connection
535 authentication and state to be used when interpreting the file request.
537 2) A new API void * lws_wsi_user(struct lws *wsi) lets you get the pointer to
538 the user data associated with the wsi, just from the wsi.
540 3) URI argument handling. Libwebsockets parses and protects URI arguments
541 like test.html?arg1=1&arg2=2, it decodes %xx uriencoding format and reduces
542 path attacks like ../.../../etc/passwd so they cannot go behind the web
543 server's /. There is a list of confirmed attacks we're proof against in
544 ./test-server/attack.sh.
546 There is a new API lws_hdr_copy_fragment that should be used now to access
547 the URI arguments (it returns the fragments length)
549 while (lws_hdr_copy_fragment(wsi, buf, sizeof(buf),
550 WSI_TOKEN_HTTP_URI_ARGS, n) > 0) {
551 lwsl_info("URI Arg %d: %s\n", ++n, buf);
554 For the example above, calling with n=0 will return "arg1=1" and n=1 "arg2=2".
555 All legal uriencodings will have been reduced in those strings.
557 lws_hdr_copy_fragment() returns the length of the x=y fragment, so it's also
558 possible to deal with arguments containing %00. If you don't care about that,
559 the returned string has '\0' appended to simplify processing.
567 - lws_callback_on_writable_all_protocol(const struct lws_protocols *protocol)
568 - lws_callback_all_protocol(const struct lws_protocols *protocol)
569 - lws_rx_flow_allow_all_protocol(lws_rx_flow_allow_all_protocol)
571 Now take an additional pointer to the lws_context in their first argument.
573 The reason for this change is struct lws_protocols has been changed to remove
574 members that lws used for private storage: so the protocols struct in now
575 truly const and may be reused serially or simultaneously by different contexts.
579 LWS_VISIBLE LWS_EXTERN int
580 lws_add_http_header_by_name(struct lws_context *context,
582 const unsigned char *name,
583 const unsigned char *value,
587 LWS_VISIBLE LWS_EXTERN int
588 lws_finalize_http_header(struct lws_context *context,
592 LWS_VISIBLE LWS_EXTERN int
593 lws_add_http_header_by_token(struct lws_context *context,
595 enum lws_token_indexes token,
596 const unsigned char *value,
600 LWS_VISIBLE LWS_EXTERN int
601 lws_add_http_header_content_length(struct lws_context *context,
603 unsigned long content_length,
606 LWS_VISIBLE LWS_EXTERN int
607 lws_add_http_header_status(struct lws_context *context, struct lws *wsi,
608 unsigned int code, unsigned char **p,
611 LWS_VISIBLE LWS_EXTERN int
612 lws_serve_http_file(struct lws_context *context, struct lws *wsi,
613 const char *file, const char *content_type,
614 const char *other_headers, int other_headers_len);
615 LWS_VISIBLE LWS_EXTERN int
616 lws_serve_http_file_fragment(struct lws_context *context, struct lws *wsi);
618 LWS_VISIBLE LWS_EXTERN int
619 lws_return_http_status(struct lws_context *context, struct lws *wsi,
620 unsigned int code, const char *html_body);
622 LWS_VISIBLE LWS_EXTERN int
623 lws_callback_on_writable(const struct lws_context *context, struct lws *wsi);
625 LWS_VISIBLE LWS_EXTERN void
626 lws_get_peer_addresses(struct lws_context *context, struct lws *wsi,
627 lws_sockfd_type fd, char *name, int name_len,
628 char *rip, int rip_len);
630 LWS_VISIBLE LWS_EXTERN int
631 lws_read(struct lws_context *context, struct lws *wsi,
632 unsigned char *buf, size_t len);
634 no longer require their initial struct lws_context * parameter.
636 3) Several older apis start with libwebsocket_ or libwebsockets_ while newer ones
637 all begin lws_. These apis have been changed to all begin with lws_.
639 To convert, search-replace
641 - libwebsockets_/lws_
643 - struct\ libwebsocket/struct\ lws
645 4) context parameter removed from user callback.
647 Since almost all apis no longer need the context as a parameter, it's no longer
648 provided at the user callback directly.
650 However if you need it, for ALL callbacks wsi is valid and has a valid context
651 pointer you can recover using lws_get_context(wsi).
654 v1.5-chrome47-firefox41
655 =======================
660 LWS_CALLBACK_CLIENT_CONNECTION_ERROR may provide an error string if in is
661 non-NULL. If so, the string has length len.
663 LWS_SERVER_OPTION_PEER_CERT_NOT_REQUIRED is available to relax the requirement
664 for peer certs if you are using the option to require client certs.
666 LWS_WITHOUT_BUILTIN_SHA1 cmake option forces lws to use SHA1() defined
667 externally, eg, byOpenSSL, and disables build of libwebsockets_SHA1()
670 v1.4-chrome43-firefox36
671 =======================
676 There's a new member in the info struct used to control context creation,
677 ssl_private_key_password, which allows passing into lws the passphrase on
680 There's a new member in struct protocols, id, which is ignored by lws but can
681 be used by the user code to mark the selected protocol by user-defined version
682 or capabliity flag information, for the case multiple versions of a protocol are
685 int lws_is_ssl(wsi) added to allow user code to know if the connection was made
686 over ssl or not. If LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT is used, both
687 ssl and non-ssl connections are possible and may need to be treated differently
690 int lws_partial_buffered(wsi) added... should be checked after any
691 libwebsocket_write that will be followed by another libwebsocket_write inside
692 the same writeable callback. If set, you can't do any more writes until the
693 writeable callback is called again. If you only do one write per writeable callback,
696 HTTP2-related: HTTP2 changes how headers are handled, lws now has new version-
697 agnositic header creation APIs. These do the right thing depending on each
698 connection's HTTP version without the user code having to know or care, except
699 to make sure to use the new APIs for headers (test-server is updated to use
700 them already, so look there for examples)
702 The APIs "render" the headers into a user-provided buffer and bump *p as it
703 is used. If *p reaches end, then the APIs return nonzero for error.
705 LWS_VISIBLE LWS_EXTERN int
706 lws_add_http_header_status(struct libwebsocket_context *context,
707 struct libwebsocket *wsi,
712 Start a response header reporting status like 200, 500, etc
714 LWS_VISIBLE LWS_EXTERN int
715 lws_add_http_header_by_name(struct libwebsocket_context *context,
716 struct libwebsocket *wsi,
717 const unsigned char *name,
718 const unsigned char *value,
723 Add a header like name: value in HTTP1.x
725 LWS_VISIBLE LWS_EXTERN int
726 lws_finalize_http_header(struct libwebsocket_context *context,
727 struct libwebsocket *wsi,
731 Finish off the headers, like add the extra \r\n in HTTP1.x
733 LWS_VISIBLE LWS_EXTERN int
734 lws_add_http_header_by_token(struct libwebsocket_context *context,
735 struct libwebsocket *wsi,
736 enum lws_token_indexes token,
737 const unsigned char *value,
742 Add a header by using a lws token as the name part. In HTTP2, this can be
743 compressed to one or two bytes.
749 protocols struct member no_buffer_all_partial_tx is removed. Under some
750 conditions like rewriting extension such as compression in use, the built-in
751 partial send buffering is the only way to deal with the problem, so turning
752 it off is deprecated.
758 HTTP2-related: API libwebsockets_serve_http_file() takes an extra parameter at
761 int other_headers_len)
763 If you are providing other headers, they must be generated using the new
764 HTTP-version-agnostic APIs, and you must provide the length of them using this
765 additional parameter.
767 struct lws_context_creation_info now has an additional member
768 SSL_CTX *provided_client_ssl_ctx you may set to an externally-initialized
769 SSL_CTX managed outside lws. Defaulting to zero keeps the existing behaviour of
770 lws managing the context, if you memset the struct to 0 or have as a filescope
771 initialized struct in bss, no need to change anything.
774 v1.3-chrome37-firefox30
775 =======================
778 CMakeLists.txt | 447 +++--
782 cmake/LibwebsocketsConfig.cmake.in | 17 +
783 cmake/LibwebsocketsConfigVersion.cmake.in | 11 +
784 config.h.cmake | 18 +
785 cross-ming.cmake | 31 +
786 cross-openwrt-makefile | 91 +
787 lib/client-handshake.c | 205 ++-
788 lib/client-parser.c | 58 +-
789 lib/client.c | 158 +-
790 lib/context.c | 341 ++++
791 lib/extension-deflate-frame.c | 2 +-
792 lib/extension.c | 178 ++
793 lib/handshake.c | 287 +---
794 lib/lextable.h | 338 ++++
796 lib/libwebsockets.c | 2089 +++--------------------
797 lib/libwebsockets.h | 253 ++-
798 lib/lws-plat-unix.c | 404 +++++
799 lib/lws-plat-win.c | 358 ++++
800 lib/minilex.c | 530 +++---
801 lib/output.c | 445 ++---
802 lib/parsers.c | 682 ++++----
803 lib/pollfd.c | 239 +++
804 lib/private-libwebsockets.h | 501 +++++-
805 lib/server-handshake.c | 274 +--
806 lib/server.c | 858 ++++++++--
807 lib/service.c | 517 ++++++
809 lib/ssl-http2.c | 78 +
810 lib/ssl.c | 571 +++++++
811 test-server/attack.sh | 101 +-
812 test-server/test-client.c | 9 +-
813 test-server/test-echo.c | 17 +-
814 test-server/test-fraggle.c | 7 -
815 test-server/test-ping.c | 12 +-
816 test-server/test-server.c | 330 ++--
817 test-server/test.html | 4 +-
818 win32port/client/client.vcxproj | 259 ---
819 win32port/client/client.vcxproj.filters | 39 -
820 .../libwebsocketswin32.vcxproj.filters | 93 -
821 win32port/server/server.vcxproj | 276 ---
822 win32port/server/server.vcxproj.filters | 51 -
823 win32port/win32helpers/gettimeofday.h | 59 +-
824 win32port/win32helpers/netdb.h | 1 -
825 win32port/win32helpers/strings.h | 0
826 win32port/win32helpers/sys/time.h | 1 -
827 win32port/win32helpers/unistd.h | 0
828 win32port/win32helpers/websock-w32.c | 104 --
829 win32port/win32helpers/websock-w32.h | 62 -
830 win32port/win32port.sln | 100 --
831 win32port/zlib/gzio.c | 3 +-
832 55 files changed, 6779 insertions(+), 5059 deletions(-)
838 POST method is supported
840 The protocol 0 / HTTP callback can now get two new kinds of callback,
841 LWS_CALLBACK_HTTP_BODY (in and len are a chunk of the body of the HTTP request)
842 and LWS_CALLBACK_HTTP_BODY_COMPLETION (the expected amount of body has arrived
843 and been passed to the user code already). These callbacks are used with the
844 post method (see the test server for details).
846 The period between the HTTP header completion and the completion of the body
847 processing is protected by a 5s timeout.
849 The chunks are stored in a malloc'd buffer of size protocols[0].rx_buffer_size.
852 New server option you can enable from user code
853 LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT allows non-SSL connections to
854 also be accepted on an SSL listening port. It's disabled unless you enable
858 Two new callbacks are added in protocols[0] that are optional for allowing
859 limited thread access to libwebsockets, LWS_CALLBACK_LOCK_POLL and
860 LWS_CALLBACK_UNLOCK_POLL.
862 If you use them, they protect internal and external poll list changes, but if
863 you want to use external thread access to libwebsocket_callback_on_writable()
864 you have to implement your locking here even if you don't use external
867 If you will use another thread for this, take a lot of care about managing
868 your list of live wsi by doing it from ESTABLISHED and CLOSED callbacks
869 (with your own locking).
871 If you configure cmake with -DLWS_WITH_LIBEV=1 then the code allowing the libev
872 eventloop instead of the default poll() one will also be compiled in. But to
873 use it, you must also set the LWS_SERVER_OPTION_LIBEV flag on the context
874 creation info struct options member.
876 IPV6 is supported and enabled by default except for Windows, you can disable
877 the support at build-time by giving -DLWS_IPV6=, and disable use of it even if
878 compiled in by making sure the flag LWS_SERVER_OPTION_DISABLE_IPV6 is set on
879 the context creation info struct options member.
881 You can give LWS_SERVER_OPTION_DISABLE_OS_CA_CERTS option flag to
882 guarantee the OS CAs will not be used, even if that support was selected at
885 Optional "token limits" may be enforced by setting the member "token_limits"
886 in struct lws_context_creation_info to point to a struct lws_token_limits.
887 NULL means no token limits used for compatibility.
893 Extra optional argument to libwebsockets_serve_http_file() allows injecion
894 of HTTP headers into the canned response. Eg, cookies may be added like
895 that without getting involved in having to send the header by hand.
897 A new info member http_proxy_address may be used at context creation time to
898 set the http proxy. If non-NULL, it overrides http_proxy environment var.
900 Cmake supports LWS_SSL_CLIENT_USE_OS_CA_CERTS defaulting to on, which gets
901 the client to use the OS CA Roots. If you're worried somebody with the
902 ability to forge for force creation of a client cert from the root CA in
903 your OS, you should disable this since your selfsigned $0 cert is a lot safer
907 v1.23-chrome32-firefox24
908 ========================
911 CMakeLists.txt | 573 ++++++++----
912 COPYING | 503 -----------
913 INSTALL | 365 --------
915 README.build | 371 ++------
916 README.coding | 63 ++
917 autogen.sh | 1578 ---------------------------------
919 cmake/FindGit.cmake | 163 ++++
920 cmake/FindOpenSSLbins.cmake | 15 +-
921 cmake/UseRPMTools.cmake | 176 ++++
922 config.h.cmake | 25 +-
923 configure.ac | 226 -----
924 cross-arm-linux-gnueabihf.cmake | 28 +
925 lib/Makefile.am | 89 --
926 lib/base64-decode.c | 98 +-
927 lib/client-handshake.c | 123 ++-
928 lib/client-parser.c | 19 +-
929 lib/client.c | 145 ++-
930 lib/daemonize.c | 4 +-
931 lib/extension.c | 2 +-
932 lib/getifaddrs.h | 4 +-
933 lib/handshake.c | 76 +-
934 lib/libwebsockets.c | 491 ++++++----
935 lib/libwebsockets.h | 164 ++--
936 lib/output.c | 214 ++++-
937 lib/parsers.c | 102 +--
938 lib/private-libwebsockets.h | 66 +-
939 lib/server-handshake.c | 5 +-
942 libwebsockets-api-doc.html | 249 +++---
943 libwebsockets.pc.in | 11 -
944 libwebsockets.spec | 14 +-
946 scripts/FindLibWebSockets.cmake | 33 +
947 scripts/kernel-doc | 1 +
948 test-server/Makefile.am | 131 ---
949 test-server/leaf.jpg | Bin 0 -> 2477518 bytes
950 test-server/test-client.c | 78 +-
951 test-server/test-echo.c | 33 +-
952 test-server/test-fraggle.c | 26 +-
953 test-server/test-ping.c | 15 +-
954 test-server/test-server.c | 197 +++-
955 test-server/test.html | 5 +-
956 win32port/win32helpers/gettimeofday.c | 74 +-
957 win32port/win32helpers/websock-w32.h | 6 +-
958 48 files changed, 2493 insertions(+), 4212 deletions(-)
964 - You can now call libwebsocket_callback_on_writable() on http connectons,
965 and get a LWS_CALLBACK_HTTP_WRITEABLE callback, the same way you can
966 regulate writes with a websocket protocol connection.
968 - A new member in the context creation parameter struct "ssl_cipher_list" is
969 added, replacing CIPHERS_LIST_STRING. NULL means use the ssl library
970 default list of ciphers.
972 - Not really an api addition, but libwebsocket_service_fd() will now zero
973 the revents field of the pollfd it was called with if it handled the
974 descriptor. So you can tell if it is a non-lws fd by checking revents
975 after the service call... if it's still nonzero, the descriptor
976 belongs to you and you need to take care of it.
978 - libwebsocket_rx_flow_allow_all_protocol(protocol) will unthrottle all
979 connections with the established protocol. It's designed to be
980 called from user server code when it sees it can accept more input
981 and may have throttled connections using the server rx flow apis
982 while it was unable to accept any other input The user server code
983 then does not have to try to track while connections it choked, this
984 will free up all of them in one call.
986 - there's a new, optional callback LWS_CALLBACK_CLOSED_HTTP which gets
987 called when an HTTP protocol socket closes
989 - for LWS_CALLBACK_FILTER_PROTOCOL_CONNECTION callback, the user_space alloc
990 has already been done before the callback happens. That means we can
991 use the user parameter to the callback to contain the user pointer, and
992 move the protocol name to the "in" parameter. The docs for this
993 callback are also updated to reflect how to check headers in there.
995 - libwebsocket_client_connect() is now properly nonblocking and async. See
996 README.coding and test-client.c for information on the callbacks you
997 can rely on controlling the async connection period with.
999 - if your OS does not support the http_proxy environment variable convention
1000 (eg, reportedly OSX), you can use a new api libwebsocket_set_proxy()
1001 to set the proxy details in between context creation and the connection
1002 action. For OSes that support http_proxy, that's used automatically.
1007 - the external poll callbacks now get the socket descriptor coming from the
1008 "in" parameter. The user parameter provides the user_space for the
1009 wsi as it normally does on the other callbacks.
1010 LWS_CALLBACK_FILTER_NETWORK_CONNECTION also has the socket descriptor
1011 delivered by @in now instead of @user.
1013 - libwebsocket_write() now returns -1 for error, or the amount of data
1014 actually accepted for send. Under load, the OS may signal it is
1015 ready to send new data on the socket, but have only a restricted
1016 amount of memory to buffer the packet compared to usual.
1022 - libwebsocket_ensure_user_space() is removed from the public api, if you
1023 were using it to get user_space, you need to adapt your code to only
1024 use user_space inside the user callback.
1026 - CIPHERS_LIST_STRING is removed
1028 - autotools build has been removed. See README.build for info on how to
1029 use CMake for your platform
1032 v1.21-chrome26-firefox18
1033 ========================
1035 - Fixes buffer overflow bug in max frame size handling if you used the
1036 default protocol buffer size. If you declared rx_buffer_size in your
1037 protocol, which is recommended anyway, your code was unaffected.
1039 v1.2-chrome26-firefox18
1040 =======================
1046 CMakeLists.txt | 544 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1047 LICENSE | 526 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1050 README.build | 258 ++++++++++++++++++++++++++++++++-----
1051 README.coding | 52 ++++++++
1052 changelog | 136 ++++++++++++++++++++
1053 cmake/FindOpenSSLbins.cmake | 33 +++++
1054 config.h.cmake | 173 +++++++++++++++++++++++++
1055 configure.ac | 22 +++-
1056 lib/Makefile.am | 20 ++-
1057 lib/base64-decode.c | 2 +-
1058 lib/client-handshake.c | 190 +++++++++++-----------------
1059 lib/client-parser.c | 88 +++++++------
1060 lib/client.c | 384 ++++++++++++++++++++++++++++++-------------------------
1061 lib/daemonize.c | 32 +++--
1062 lib/extension-deflate-frame.c | 58 +++++----
1063 lib/extension-deflate-stream.c | 19 ++-
1064 lib/extension-deflate-stream.h | 4 +-
1065 lib/extension.c | 11 +-
1066 lib/getifaddrs.c | 315 +++++++++++++++++++++++-----------------------
1067 lib/getifaddrs.h | 30 ++---
1068 lib/handshake.c | 124 +++++++++++-------
1069 lib/libwebsockets.c | 736 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------
1070 lib/libwebsockets.h | 237 ++++++++++++++++++++++------------
1071 lib/output.c | 192 +++++++++++-----------------
1072 lib/parsers.c | 966 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------
1073 lib/private-libwebsockets.h | 225 +++++++++++++++++++++------------
1074 lib/server-handshake.c | 82 ++++++------
1075 lib/server.c | 96 +++++++-------
1076 libwebsockets-api-doc.html | 189 ++++++++++++++++++----------
1077 libwebsockets.spec | 17 +--
1078 test-server/attack.sh | 148 ++++++++++++++++++++++
1079 test-server/test-client.c | 125 +++++++++---------
1080 test-server/test-echo.c | 31 +++--
1081 test-server/test-fraggle.c | 32 ++---
1082 test-server/test-ping.c | 52 ++++----
1083 test-server/test-server.c | 129 ++++++++++++-------
1084 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj | 279 ----------------------------------------
1085 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj.filters | 23 +++-
1086 41 files changed, 4398 insertions(+), 2219 deletions(-)
1092 - lws_get_library_version() returns a const char * with a string like
1093 "1.1 9e7f737", representing the library version from configure.ac
1094 and the git HEAD hash the library was built from
1096 - TCP Keepalive can now optionally be applied to all lws sockets, on Linux
1097 also with controllable timeout, number of probes and probe interval.
1098 (On BSD type OS, you can only use system default settings for the
1099 timing and retries, although enabling it is supported by setting
1100 ka_time to nonzero, the exact value has no meaning.)
1101 This enables detection of idle connections which are logically okay,
1102 but are in fact dead, due to network connectivity issues at the server,
1103 client, or any intermediary. By default it's not enabled, but you
1104 can enable it by setting a non-zero timeout (in seconds) at the new
1105 ka_time member at context creation time.
1107 - Two new optional user callbacks added, LWS_CALLBACK_PROTOCOL_DESTROY which
1108 is called one-time per protocol as the context is being destroyed, and
1109 LWS_CALLBACK_PROTOCOL_INIT which is called when the context is created
1110 and the protocols are added, again it's a one-time affair.
1111 This lets you manage per-protocol allocations properly including
1112 cleaning up after yourself when the server goes down.
1117 - libwebsocket_create_context() has changed from taking a ton of parameters
1118 to just taking a pointer to a struct containing the parameters. The
1119 struct lws_context_creation_info is in libwebsockets.h, the members
1120 are in the same order as when they were parameters to the call
1121 previously. The test apps are all updated accordingly so you can
1122 see example code there.
1124 - Header tokens are now deleted after the websocket connection is
1125 established. Not just the header data is saved, but the pointer and
1126 length array is also removed from (union) scope saving several hundred
1127 bytes per connection once it is established
1129 - struct libwebsocket_protocols has a new member rx_buffer_size, this
1130 controls rx buffer size per connection of that protocol now. Sources
1131 for apps built against older versions of the library won't declare
1132 this in their protocols, defaulting it to 0. Zero buffer is legal,
1133 it causes a default buffer to be allocated (currently 4096)
1135 If you want to receive only atomic frames in your user callback, you
1136 should set this to greater than your largest frame size. If a frame
1137 comes that exceeds that, no error occurs but the callback happens as
1138 soon as the buffer limit is reached, and again if it is reached again
1139 or the frame completes. You can detect that has happened by seeing
1140 there is still frame content pending using
1141 libwebsockets_remaining_packet_payload()
1143 By correctly setting this, you can save a lot of memory when your
1144 protocol has small frames (see the test server and client sources).
1146 - LWS_MAX_HEADER_LEN now defaults to 1024 and is the total amount of known
1147 header payload lws can cope with, that includes the GET URL, origin
1148 etc. Headers not understood by lws are ignored and their payload
1149 not included in this.
1155 - The configuration-time option MAX_USER_RX_BUFFER has been replaced by a
1156 buffer size chosen per-protocol. For compatibility, there's a default
1157 of 4096 rx buffer, but user code should set the appropriate size for
1158 the protocol frames.
1160 - LWS_INITIAL_HDR_ALLOC and LWS_ADDITIONAL_HDR_ALLOC are no longer needed
1161 and have been removed. There's a new header management scheme that
1162 handles them in a much more compact way.
1164 - libwebsockets_hangup_on_client() is removed. If you want to close the
1165 connection you must do so from the user callback and by returning
1168 - libwebsocket_close_and_free_session() is now private to the library code
1169 only and not exposed for user code. If you want to close the
1170 connection, you must do so from the user callback by returning -1
1177 - Cmake project file added, aimed initially at Windows support: this replaces
1178 the visual studio project files that were in the tree until now.
1180 - CyaSSL now supported in place of OpenSSL (--use-cyassl on configure)
1182 - PATH_MAX or MAX_PATH no longer needed
1184 - cutomizable frame rx buffer size by protocol
1186 - optional TCP keepalive so dead peers can be detected, can be enabled at
1187 context-creation time
1189 - valgrind-clean: no SSL or CyaSSL: completely clean. With OpenSSL, 88 bytes
1190 lost at OpenSSL library init and symptomless reports of uninitialized
1191 memory usage... seems to be a known and ignored problem at OpenSSL
1193 - By default debug is enabled and the library is built for -O0 -g to faclitate
1194 that. Use --disable-debug configure option to build instead with -O4
1195 and no -g (debug info), obviously providing best performance and
1196 reduced binary size.
1198 - 1.0 introduced some code to try to not deflate small frames, however this
1199 seems to break when confronted with a mixture of frames above and
1200 below the threshold, so it's removed. Veto the compression extension
1201 in your user callback if you will typically have very small frames.
1203 - There are many memory usage improvements, both a reduction in malloc/
1204 realloc and architectural changes. A websocket connection now
1205 consumes only 296 bytes with SSL or 272 bytes without on x86_64,
1206 during header processing an additional 1262 bytes is allocated in a
1207 single malloc, but is freed when the websocket connection starts.
1208 The RX frame buffer defined by the protocol in user
1209 code is also allocated per connection, this represents the largest
1210 frame you can receive atomically in that protocol.
1212 - On ARM9 build, just http+ws server no extensions or ssl, <12Kbytes .text
1213 and 112 bytes per connection (+1328 only during header processing)
1216 v1.1-chrome26-firefox18
1217 =======================
1223 README-test-server | 291 ---
1224 README.build | 239 ++
1225 README.coding | 138 ++
1227 README.test-apps | 272 +++
1228 configure.ac | 116 +-
1229 lib/Makefile.am | 55 +-
1230 lib/base64-decode.c | 5 +-
1231 lib/client-handshake.c | 121 +-
1232 lib/client-parser.c | 394 ++++
1233 lib/client.c | 807 +++++++
1234 lib/daemonize.c | 212 ++
1235 lib/extension-deflate-frame.c | 132 +-
1236 lib/extension-deflate-stream.c | 12 +-
1237 lib/extension-x-google-mux.c | 1223 ----------
1238 lib/extension-x-google-mux.h | 96 -
1239 lib/extension.c | 8 -
1240 lib/getifaddrs.c | 271 +++
1241 lib/getifaddrs.h | 76 +
1242 lib/handshake.c | 582 +----
1243 lib/libwebsockets.c | 2493 ++++++---------------
1244 lib/libwebsockets.h | 115 +-
1246 lib/minilex.c | 440 ++++
1247 lib/output.c | 628 ++++++
1248 lib/parsers.c | 2016 +++++------------
1249 lib/private-libwebsockets.h | 284 +--
1250 lib/server-handshake.c | 275 +++
1251 lib/server.c | 377 ++++
1252 libwebsockets-api-doc.html | 300 +--
1254 test-server/Makefile.am | 111 +-
1255 test-server/libwebsockets.org-logo.png | Bin 0 -> 7029 bytes
1256 test-server/test-client.c | 45 +-
1257 test-server/test-echo.c | 330 +++
1258 test-server/test-fraggle.c | 20 +-
1259 test-server/test-ping.c | 22 +-
1260 test-server/test-server-extpoll.c | 554 -----
1261 test-server/test-server.c | 349 ++-
1262 test-server/test.html | 3 +-
1263 win32port/zlib/ZLib.vcxproj | 749 ++++---
1264 win32port/zlib/ZLib.vcxproj.filters | 188 +-
1265 win32port/zlib/adler32.c | 348 ++-
1266 win32port/zlib/compress.c | 160 +-
1267 win32port/zlib/crc32.c | 867 ++++----
1268 win32port/zlib/crc32.h | 882 ++++----
1269 win32port/zlib/deflate.c | 3799 +++++++++++++++-----------------
1270 win32port/zlib/deflate.h | 688 +++---
1271 win32port/zlib/gzclose.c | 50 +-
1272 win32port/zlib/gzguts.h | 325 ++-
1273 win32port/zlib/gzlib.c | 1157 +++++-----
1274 win32port/zlib/gzread.c | 1242 ++++++-----
1275 win32port/zlib/gzwrite.c | 1096 +++++----
1276 win32port/zlib/infback.c | 1272 ++++++-----
1277 win32port/zlib/inffast.c | 680 +++---
1278 win32port/zlib/inffast.h | 22 +-
1279 win32port/zlib/inffixed.h | 188 +-
1280 win32port/zlib/inflate.c | 2976 +++++++++++++------------
1281 win32port/zlib/inflate.h | 244 +-
1282 win32port/zlib/inftrees.c | 636 +++---
1283 win32port/zlib/inftrees.h | 124 +-
1284 win32port/zlib/trees.c | 2468 +++++++++++----------
1285 win32port/zlib/trees.h | 256 +--
1286 win32port/zlib/uncompr.c | 118 +-
1287 win32port/zlib/zconf.h | 934 ++++----
1288 win32port/zlib/zlib.h | 3357 ++++++++++++++--------------
1289 win32port/zlib/zutil.c | 642 +++---
1290 win32port/zlib/zutil.h | 526 ++---
1291 69 files changed, 19556 insertions(+), 20145 deletions(-)
1296 - libwebsockets_serve_http_file() now takes a context as first argument
1298 - libwebsockets_get_peer_addresses() now takes a context and wsi as first
1305 - lwsl_...() logging apis, default to stderr but retargetable by user code;
1306 may be used also by user code
1308 - lws_set_log_level() set which logging apis are able to emit (defaults to
1309 notice, warn, err severities), optionally set the emit callback
1311 - lwsl_emit_syslog() helper callback emits to syslog
1313 - lws_daemonize() helper code that forks the app into a headless daemon
1314 properly, maintains a lock file with pid in suitable for sysvinit etc to
1317 - LWS_CALLBACK_HTTP_FILE_COMPLETION callback added since http file
1318 transfer is now asynchronous (see test server code)
1320 - lws_frame_is_binary() from a wsi pointer, let you know if the received
1321 data was sent in BINARY mode
1327 - libwebsockets_fork_service_loop() - no longer supported (had intractable problems)
1328 arrange your code to act from the user callback instead from same
1329 process context as the service loop
1331 - libwebsockets_broadcast() - use libwebsocket_callback_on_writable[_all_protocol]()
1332 instead from same process context as the service loop. See the test apps
1335 - x-google-mux() removed until someone wants it
1337 - pre -v13 (ancient) protocol support removed
1343 - echo test server and client compatible with echo.websocket.org added
1345 - many new configure options (see README.build) to reduce footprint of the
1346 library to what you actually need, eg, --without-client and
1349 - http + websocket server can build to as little as 12K .text for ARM
1351 - no more MAX_CLIENTS limitation; adapts to support the max number of fds
1352 allowed to the process by ulimit, defaults to 1024 on Fedora and
1353 Ubuntu. Use ulimit to control this without needing to configure
1354 the library. Code here is smaller and faster.
1356 - adaptive ratio of listen socket to connection socket service allows
1357 good behaviour under Apache ab test load. Tested with thousands
1358 of simultaneous connections
1360 - reduction in per-connection memory footprint by moving to a union to hold
1361 mutually-exclusive state for the connection
1363 - robustness: Out of Memory taken care of for all allocation code now
1365 - internal getifaddrs option if your toolchain lacks it (some uclibc)
1367 - configurable memory limit for deflate operations
1369 - improvements in SSL code nonblocking operation, possible hang solved,
1370 some SSL operations broken down into pollable states so there is
1371 no library blocking, timeout coverage for SSL_connect
1373 - extpoll test server merged into single test server source
1375 - robustness: library should deal with all recoverable socket conditions
1377 - rx flowcontrol for backpressure notification fixed and implmeneted
1378 correctly in the test server
1380 - optimal lexical parser added for header processing; all headers in a
1381 single 276-byte state table
1383 - latency tracking api added (configure --with-latency)
1385 - Improved in-tree documentation, REAME.build, README.coding,
1386 README.test-apps, changelog
1391 v1.0-chrome25-firefox17 (6cd1ea9b005933f)