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) If you enable -DLWS_WITH_HTTP_PROXY=1 at cmake, the test server has a
85 new URI path http://localhost:7681/proxytest If you visit here, a client
86 connection to http://example.com:80 is spawned, and the results piped on
87 to your original connection.
89 10) Also with LWS_WITH_HTTP_PROXY enabled at cmake, lws wants to link to an
90 additional library, "libhubbub". This allows lws to do html rewriting on the
91 fly, adjusting proxied urls in a lightweight and fast way.
93 11) There's a new context creation flag LWS_SERVER_OPTION_DO_SSL_GLOBAL_INIT,
94 this is included automatically if you give any other SSL-related option flag.
95 If you give no SSL-related option flag, nor this one directly, then even
96 though SSL support may be compiled in, it is never initialized nor used for the
97 whole lifetime of the lws context.
99 Conversely in order to prepare the context to use SSL, even though, eg, you
100 are not listening on SSL but will use SSL client connections later, you must
101 give this flag explicitly to make sure SSL is initialized.
107 1) MINOR APIBREAK There's a new member in struct lws_context_creation_info, ecdh_curve,
108 which lets you set the name of the ECDH curve OpenSSL should use. By
109 default (if you leave ecdh_curve NULL) it will use "prime256v1"
111 2) MINOR NEWAPI It was already possible to adopt a foreign socket that had not
112 been read from using lws_adopt_socket() since v1.7. Now you can adopt a
113 partially-used socket if you don't need SSL, by passing it what you read
114 so it can drain that before reading from the socket.
116 LWS_VISIBLE LWS_EXTERN struct lws *
117 lws_adopt_socket_readbuf(struct lws_context *context, lws_sockfd_type accept_fd,
118 const char *readbuf, size_t len);
120 3) MINOR NEWAPI CGI type "network io" subprocess execution is now possible from
123 LWS_VISIBLE LWS_EXTERN int
124 lws_cgi(struct lws *wsi, char * const *exec_array, int script_uri_path_len,
127 LWS_VISIBLE LWS_EXTERN int
128 lws_cgi_kill(struct lws *wsi);
130 To use it, you must first set the cmake option
132 $ cmake .. -DLWS_WITH_CGI=1
134 See test-server-http.c and test server path
136 http://localhost:7681/cgitest
138 stdin gets http body, you can test it with wget
140 $ echo hello > hello.txt
141 $ wget http://localhost:7681/cgitest --post-file=hello.txt -O- --quiet
145 The test script returns text/html table showing /proc/meminfo. But the cgi
146 support is complete enough to run cgit cgi.
148 4) There is a helper api for forming logging timestamps
151 lwsl_timestamp(int level, char *p, int len)
153 this generates this kind of timestamp for use as logging preamble
155 lwsts[13116]: [2016/01/25 14:52:52:8386] NOTICE: Initial logging level 7
157 5) struct lws_client_connect_info has a new member
161 If it's NULL, then everything happens as before, lws_client_connect_via_info()
162 makes a ws or wss connection to the address given.
164 If you set method to a valid http method like "GET", though, then this method
165 is used and the connection remains in http[s], it's not upgraded to ws[s].
167 So with this, you can perform http[s] client operations as well as ws[s] ones.
169 There are 4 new related callbacks
171 LWS_CALLBACK_ESTABLISHED_CLIENT_HTTP = 44,
172 LWS_CALLBACK_CLOSED_CLIENT_HTTP = 45,
173 LWS_CALLBACK_RECEIVE_CLIENT_HTTP = 46,
174 LWS_CALLBACK_COMPLETED_CLIENT_HTTP = 47,
176 6) struct lws_client_connect_info has a new member
178 const char *parent_wsi
180 if non-NULL, the client wsi is set to be a child of parent_wsi. This ensures
181 if parent_wsi closes, then the client child is closed just before.
183 7) If you're using SSL, there's a new context creation-time option flag
184 LWS_SERVER_OPTION_REDIRECT_HTTP_TO_HTTPS. If you give this, non-ssl
185 connections to the server listen port are accepted and receive a 301
186 redirect to / on the same host and port using https://
188 8) User code may set per-connection extension options now, using a new api
189 "lws_set_extension_option()".
191 This should be called from the ESTABLISHED callback like this
193 lws_set_extension_option(wsi, "permessage-deflate",
194 "rx_buf_size", "12"); /* 1 << 12 */
196 If the extension is not active (missing or not negotiated for the
197 connection, or extensions are disabled on the library) the call is
198 just returns -1. Otherwise the connection's extension has its
199 named option changed.
201 The extension may decide to alter or disallow the change, in the
202 example above permessage-deflate restricts the size of his rx
203 output buffer also considering the protocol's rx_buf_size member.
206 New application lwsws
207 ---------------------
209 A libwebsockets-based general webserver is built by default now, lwsws.
211 It's configured by JSON, by default in
215 which contains global lws context settings like this
228 which contains zero or more files describing vhosts, like this
232 { "name": "warmcat.com",
234 "host-ssl-key": "/etc/pki/tls/private/warmcat.com.key",
235 "host-ssl-cert": "/etc/pki/tls/certs/warmcat.com.crt",
236 "host-ssl-ca": "/etc/pki/tls/certs/warmcat.com.cer",
239 { "home": "file:///var/www/warmcat.com" },
240 { "default": "index.html" }
256 1) There is now a "permessage-deflate" / RFC7692 implementation. It's very
257 similar to "deflate-frame" we have offered for a long while; deflate-frame is
258 now provided as an alias of permessage-deflate.
260 The main differences are that the new permessage-deflate implementation:
262 - properly performs streaming respecting input and output buffer limits. The
263 old deflate-frame implementation could only work on complete deflate input
264 and produce complete inflate output for each frame. The new implementation
265 only mallocs buffers at initialization.
267 - goes around the event loop after each input package is processed allowing
268 interleaved output processing. The RX flow control api can be used to
269 force compressed input processing to match the rate of compressed output
270 processing (test--echo shows an example of how to do this).
272 - when being "deflate-frame" for compatibility he uses the same default zlib
273 settings as the old "deflate-frame", but instead of exponentially increasing
274 malloc allocations until the whole output will fit, he observes the default
275 input and output chunking buffer sizes of "permessage-deflate", that's
276 1024 in and 1024 out at a time.
278 2) deflate-stream has been disabled for many versions (for over a year) and is
279 now removed. Browsers are now standardizing on "permessage-deflate" / RFC7692
281 3) struct lws_extension is simplified, and lws extensions now have a public
282 api (their callback) for use in user code to compose extensions and options
283 the user code wants. lws_get_internal_exts() is deprecated but kept around
284 as a NOP. The changes allow one extension implementation to go by different
285 names and allows the user client code to control option offers per-ext.
287 The test client and server are updated to use the new way. If you use
288 the old way it should still work, but extensions will be disabled until you
291 Extensions are now responsible for allocating and per-instance private struct
292 at instance construction time and freeing it when the instance is destroyed.
293 Not needing to know the size means the extension's struct can be opaque
300 1) The info struct gained three new members
302 - max_http_header_data: 0 for default (1024) or set the maximum amount of known
303 http header payload that lws can deal with. Payload in unknown http
304 headers is dropped silently. If for some reason you need to send huge
305 cookies or other HTTP-level headers, you can now increase this at context-
308 - max_http_header_pool: 0 for default (16) or set the maximum amount of http
309 headers that can be tracked by lws in this context. For the server, if
310 the header pool is completely in use then accepts on the listen socket
311 are disabled until one becomes free. For the client, if you simultaneously
312 have pending connects for more than this number of client connections,
313 additional connects will fail until some of the pending connections timeout
316 - timeout_secs: 0 for default (currently 20s), or set the library's
317 network activity timeout to the given number of seconds
319 HTTP header processing in lws only exists until just after the first main
320 callback after the HTTP handshake... for ws connections that is ESTABLISHED and
321 for HTTP connections the HTTP callback.
323 So these settings are not related to the maximum number of simultaneous
324 connections, but the number of HTTP handshakes that may be expected or ongoing,
325 or have just completed, at one time. The reason it's useful is it changes the
326 memory allocation for header processing to be one-time at context creation
327 instead of every time there is a new connection, and gives you control over
330 Setting max_http_header_pool to 1 is fine it will just queue incoming
331 connections before the accept as necessary, you can still have as many
332 simultaneous post-header connections as you like. Since the http header
333 processing is completed and the allocation released after ESTABLISHED or the
334 HTTP callback, even with a pool of 1 many connections can be handled rapidly.
336 2) There is a new callback that allows the user code to get acccess to the
337 optional close code + aux data that may have been sent by the peer.
339 LWS_CALLBACK_WS_PEER_INITIATED_CLOSE:
340 The peer has sent an unsolicited Close WS packet. @in and
341 @len are the optional close code (first 2 bytes, network
342 order) and the optional additional information which is not
343 defined in the standard, and may be a string or non-human-
345 If you return 0 lws will echo the close and then close the
346 connection. If you return nonzero lws will just close the
349 As usual not handling it does the right thing, if you're not interested in it
352 The test server has "open and close" testing buttons at the bottom, if you
353 open and close that connection, on close it will send a close code 3000 decimal
354 and the string "Bye!" as the aux data.
356 The test server dumb-increment callback handles this callback reason and prints
358 lwsts[15714]: LWS_CALLBACK_WS_PEER_INITIATED_CLOSE: len 6
359 lwsts[15714]: 0: 0x0B
360 lwsts[15714]: 1: 0xB8
361 lwsts[15714]: 2: 0x42
362 lwsts[15714]: 3: 0x79
363 lwsts[15714]: 4: 0x65
364 lwsts[15714]: 5: 0x21
366 3) There is a new API to allow the user code to control the content of the
367 close frame sent when about to return nonzero from the user callback to
368 indicate the connection should close.
371 * lws_close_reason - Set reason and aux data to send with Close packet
372 * If you are going to return nonzero from the callback
373 * requesting the connection to close, you can optionally
374 * call this to set the reason the peer will be told if
377 * @wsi: The websocket connection to set the close reason on
378 * @status: A valid close status from websocket standard
379 * @buf: NULL or buffer containing up to 124 bytes of auxiliary data
380 * @len: Length of data in @buf to send
382 LWS_VISIBLE LWS_EXTERN void
383 lws_close_reason(struct lws *wsi, enum lws_close_status status,
384 unsigned char *buf, size_t len);
386 An extra button is added to the "open and close" test server page that requests
387 that the test server close the connection from his end.
389 The test server code will do so by
391 lws_close_reason(wsi, LWS_CLOSE_STATUS_GOINGAWAY,
392 (unsigned char *)"seeya", 5);
395 The browser shows the close code and reason he received
397 websocket connection CLOSED, code: 1001, reason: seeya
399 4) There's a new context creation time option flag
401 LWS_SERVER_OPTION_VALIDATE_UTF8
403 if you set it in info->options, then TEXT and CLOSE frames will get checked to
404 confirm that they contain valid UTF-8. If they don't, the connection will get
407 5) ECDH Certs are now supported. Enable the CMake option
409 cmake .. -DLWS_SSL_SERVER_WITH_ECDH_CERT=1
411 **and** the info->options flag
413 LWS_SERVER_OPTION_SSL_ECDH
415 to build in support and select it at runtime.
417 6) There's a new api lws_parse_uri() that simplifies chopping up
418 https://xxx:yyy/zzz uris into parts nicely. The test client now uses this
419 to allow proper uris as well as the old address style.
421 7) SMP support is integrated into LWS without any internal threading. It's
422 very simple to use, libwebsockets-test-server-pthread shows how to do it,
423 use -j <n> argument there to control the number of service threads up to 32.
425 Two new members are added to the info struct
427 unsigned int count_threads;
428 unsigned int fd_limit_per_thread;
430 leave them at the default 0 to get the normal singlethreaded service loop.
432 Set count_threads to n to tell lws you will have n simultaneous service threads
433 operating on the context.
435 There is still a single listen socket on one port, no matter how many
438 When a connection is made, it is accepted by the service thread with the least
439 connections active to perform load balancing.
441 The user code is responsible for spawning n threads running the service loop
442 associated to a specific tsi (Thread Service Index, 0 .. n - 1). See
443 the libwebsockets-test-server-pthread for how to do.
445 If you leave fd_limit_per_thread at 0, then the process limit of fds is shared
446 between the service threads; if you process was allowed 1024 fds overall then
447 each thread is limited to 1024 / n.
449 You can set fd_limit_per_thread to a nonzero number to control this manually, eg
450 the overall supported fd limit is less than the process allowance.
452 You can control the context basic data allocation for multithreading from Cmake
453 using -DLWS_MAX_SMP=, if not given it's set to 32. The serv_buf allocation
454 for the threads (currently 4096) is made at runtime only for active threads.
456 Because lws will limit the requested number of actual threads supported
457 according to LWS_MAX_SMP, there is an api lws_get_count_threads(context) to
458 discover how many threads were actually allowed when the context was created.
460 It's required to implement locking in the user code in the same way that
461 libwebsockets-test-server-pthread does it, for the FD locking callbacks.
463 If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the
464 library. If more than 1, a small amount of pthread mutex code is built into
469 LWS_VISIBLE struct lws *
470 lws_adopt_socket(struct lws_context *context, lws_sockfd_type accept_fd)
472 allows foreign sockets accepted by non-lws code to be adopted by lws as if they
473 had just been accepted by lws' own listen socket.
475 9) X-Real-IP: header has been added as WSI_TOKEN_HTTP_X_REAL_IP
477 10) Libuv support is added, there are new related user apis
479 typedef void (lws_uv_signal_cb_t)(uv_loop_t *l, uv_signal_t *w, int revents);
481 LWS_VISIBLE LWS_EXTERN int
482 lws_uv_sigint_cfg(struct lws_context *context, int use_uv_sigint,
483 lws_uv_signal_cb_t *cb);
485 LWS_VISIBLE LWS_EXTERN int
486 lws_uv_initloop(struct lws_context *context, uv_loop_t *loop, int tsi);
489 lws_uv_sigint_cb(uv_loop_t *loop, uv_signal_t *watcher, int revents);
499 1) LWS_SEND_BUFFER_POST_PADDING is now 0 and deprecated. You can remove it; if
500 you still use it, obviously it does nothing. Old binary code with nonzero
501 LWS_SEND_BUFFER_POST_PADDING is perfectly compatible, the old code just
502 allocated a buffer bigger than the library is going to use.
504 The example apps no longer use LWS_SEND_BUFFER_POST_PADDING.
506 The only path who made use of it was sending with LWS_WRITE_CLOSE --->
508 2) Because of lws_close_reason() formalizing handling close frames,
509 LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send
510 close frames...close frame content should be managed using lws_close_reason()
513 3) We check for invalid CLOSE codes and complain about protocol violation in
514 our close code. But it changes little since we were in the middle of closing
517 4) zero-length RX frames and zero length TX frames are now allowed.
519 5) Pings and close used to be limited to 124 bytes, the correct limit is 125
520 so that is now also allowed.
522 6) LWS_PRE is provided as a synonym for LWS_SEND_BUFFER_PRE_PADDING, either is
525 7) There's generic support for RFC7462 style extension options built into the
526 library now. As a consequence, a field "options" is added to lws_extension.
527 It can be NULL if there are no options on the extension. Extension internal
528 info is part of the public abi because extensions may be implemented outside
531 8) WSI_TOKEN_PROXY enum was accidentally defined to collide with another token
532 of value 73. That's now corrected and WSI_TOKEN_PROXY moved to his own place at
535 9) With the addition of libuv support, libev is not the only event loop
536 library in town and his api names must be elaborated with _ev_
538 Callback typedef: lws_signal_cb ---> lws_ev_signal_cb_t
539 lws_sigint_cfg --> lws_ev_sigint_cfg
540 lws_initloop --> lws_ev_initloop
541 lws_sigint_cb --> lws_ev_sigint_cb
543 10) Libev support is made compatible with multithreaded service,
544 lws_ev_initloop (was lws_initloop) gets an extra argument for the
545 thread service index (use 0 if you will just have 1 service thread).
547 LWS_VISIBLE LWS_EXTERN int
548 lws_ev_initloop(struct lws_context *context, ev_loop_t *loop, int tsi);
551 v1.6.0-chrome48-firefox42
552 =======================
554 Major API improvements
555 ----------------------
557 v1.6.0 has many cleanups and improvements in the API. Although at first it
558 looks pretty drastic, user code will only need four actions to update it.
560 - Do the three search/replaces in your user code, /libwebsocket_/lws_/,
561 /libwebsockets_/lws_/, and /struct\ libwebsocket/struct\ lws/
563 - Remove the context parameter from your user callbacks
565 - Remove context as the first parameter from the "Eleven APIS" listed in the
566 User Api Changes section
568 - Add lws_get_context(wsi) as the first parameter on the "Three APIS" listed
569 in the User Api Changes section, and anywhere else you still need context
571 That's it... generally only a handful of the 14 affected APIs are actually in
572 use in your user code and you can find them quickest by compiling and visiting
573 the errors each in turn. And the end results are much cleaner, more
574 predictable and maintainable.
580 1) lws now exposes his internal platform file abstraction in a way that can be
581 both used by user code to make it platform-agnostic, and be overridden or
582 subclassed by user code. This allows things like handling the URI "directory
583 space" as a virtual filesystem that may or may not be backed by a regular
584 filesystem. One example use is serving files from inside large compressed
585 archive storage without having to unpack anything except the file being
588 The test server shows how to use it, basically the platform-specific part of
589 lws prepares a file operations structure that lives in the lws context.
591 Helpers are provided to also leverage these platform-independent file handling
594 static inline lws_filefd_type
595 lws_plat_file_open(struct lws *wsi, const char *filename,
596 unsigned long *filelen, int flags)
598 lws_plat_file_close(struct lws *wsi, lws_filefd_type fd)
600 static inline unsigned long
601 lws_plat_file_seek_cur(struct lws *wsi, lws_filefd_type fd, long offset)
604 lws_plat_file_read(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
605 unsigned char *buf, unsigned long len)
608 lws_plat_file_write(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
609 unsigned char *buf, unsigned long len)
611 The user code can also override or subclass the file operations, to either
612 wrap or replace them. An example is shown in test server.
614 A wsi can be associated with the file activity, allowing per-connection
615 authentication and state to be used when interpreting the file request.
617 2) A new API void * lws_wsi_user(struct lws *wsi) lets you get the pointer to
618 the user data associated with the wsi, just from the wsi.
620 3) URI argument handling. Libwebsockets parses and protects URI arguments
621 like test.html?arg1=1&arg2=2, it decodes %xx uriencoding format and reduces
622 path attacks like ../.../../etc/passwd so they cannot go behind the web
623 server's /. There is a list of confirmed attacks we're proof against in
624 ./test-server/attack.sh.
626 There is a new API lws_hdr_copy_fragment that should be used now to access
627 the URI arguments (it returns the fragments length)
629 while (lws_hdr_copy_fragment(wsi, buf, sizeof(buf),
630 WSI_TOKEN_HTTP_URI_ARGS, n) > 0) {
631 lwsl_info("URI Arg %d: %s\n", ++n, buf);
634 For the example above, calling with n=0 will return "arg1=1" and n=1 "arg2=2".
635 All legal uriencodings will have been reduced in those strings.
637 lws_hdr_copy_fragment() returns the length of the x=y fragment, so it's also
638 possible to deal with arguments containing %00. If you don't care about that,
639 the returned string has '\0' appended to simplify processing.
647 - lws_callback_on_writable_all_protocol(const struct lws_protocols *protocol)
648 - lws_callback_all_protocol(const struct lws_protocols *protocol)
649 - lws_rx_flow_allow_all_protocol(lws_rx_flow_allow_all_protocol)
651 Now take an additional pointer to the lws_context in their first argument.
653 The reason for this change is struct lws_protocols has been changed to remove
654 members that lws used for private storage: so the protocols struct in now
655 truly const and may be reused serially or simultaneously by different contexts.
659 LWS_VISIBLE LWS_EXTERN int
660 lws_add_http_header_by_name(struct lws_context *context,
662 const unsigned char *name,
663 const unsigned char *value,
667 LWS_VISIBLE LWS_EXTERN int
668 lws_finalize_http_header(struct lws_context *context,
672 LWS_VISIBLE LWS_EXTERN int
673 lws_add_http_header_by_token(struct lws_context *context,
675 enum lws_token_indexes token,
676 const unsigned char *value,
680 LWS_VISIBLE LWS_EXTERN int
681 lws_add_http_header_content_length(struct lws_context *context,
683 unsigned long content_length,
686 LWS_VISIBLE LWS_EXTERN int
687 lws_add_http_header_status(struct lws_context *context, struct lws *wsi,
688 unsigned int code, unsigned char **p,
691 LWS_VISIBLE LWS_EXTERN int
692 lws_serve_http_file(struct lws_context *context, struct lws *wsi,
693 const char *file, const char *content_type,
694 const char *other_headers, int other_headers_len);
695 LWS_VISIBLE LWS_EXTERN int
696 lws_serve_http_file_fragment(struct lws_context *context, struct lws *wsi);
698 LWS_VISIBLE LWS_EXTERN int
699 lws_return_http_status(struct lws_context *context, struct lws *wsi,
700 unsigned int code, const char *html_body);
702 LWS_VISIBLE LWS_EXTERN int
703 lws_callback_on_writable(const struct lws_context *context, struct lws *wsi);
705 LWS_VISIBLE LWS_EXTERN void
706 lws_get_peer_addresses(struct lws_context *context, struct lws *wsi,
707 lws_sockfd_type fd, char *name, int name_len,
708 char *rip, int rip_len);
710 LWS_VISIBLE LWS_EXTERN int
711 lws_read(struct lws_context *context, struct lws *wsi,
712 unsigned char *buf, size_t len);
714 no longer require their initial struct lws_context * parameter.
716 3) Several older apis start with libwebsocket_ or libwebsockets_ while newer ones
717 all begin lws_. These apis have been changed to all begin with lws_.
719 To convert, search-replace
721 - libwebsockets_/lws_
723 - struct\ libwebsocket/struct\ lws
725 4) context parameter removed from user callback.
727 Since almost all apis no longer need the context as a parameter, it's no longer
728 provided at the user callback directly.
730 However if you need it, for ALL callbacks wsi is valid and has a valid context
731 pointer you can recover using lws_get_context(wsi).
734 v1.5-chrome47-firefox41
735 =======================
740 LWS_CALLBACK_CLIENT_CONNECTION_ERROR may provide an error string if in is
741 non-NULL. If so, the string has length len.
743 LWS_SERVER_OPTION_PEER_CERT_NOT_REQUIRED is available to relax the requirement
744 for peer certs if you are using the option to require client certs.
746 LWS_WITHOUT_BUILTIN_SHA1 cmake option forces lws to use SHA1() defined
747 externally, eg, byOpenSSL, and disables build of libwebsockets_SHA1()
750 v1.4-chrome43-firefox36
751 =======================
756 There's a new member in the info struct used to control context creation,
757 ssl_private_key_password, which allows passing into lws the passphrase on
760 There's a new member in struct protocols, id, which is ignored by lws but can
761 be used by the user code to mark the selected protocol by user-defined version
762 or capabliity flag information, for the case multiple versions of a protocol are
765 int lws_is_ssl(wsi) added to allow user code to know if the connection was made
766 over ssl or not. If LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT is used, both
767 ssl and non-ssl connections are possible and may need to be treated differently
770 int lws_partial_buffered(wsi) added... should be checked after any
771 libwebsocket_write that will be followed by another libwebsocket_write inside
772 the same writeable callback. If set, you can't do any more writes until the
773 writeable callback is called again. If you only do one write per writeable callback,
776 HTTP2-related: HTTP2 changes how headers are handled, lws now has new version-
777 agnositic header creation APIs. These do the right thing depending on each
778 connection's HTTP version without the user code having to know or care, except
779 to make sure to use the new APIs for headers (test-server is updated to use
780 them already, so look there for examples)
782 The APIs "render" the headers into a user-provided buffer and bump *p as it
783 is used. If *p reaches end, then the APIs return nonzero for error.
785 LWS_VISIBLE LWS_EXTERN int
786 lws_add_http_header_status(struct libwebsocket_context *context,
787 struct libwebsocket *wsi,
792 Start a response header reporting status like 200, 500, etc
794 LWS_VISIBLE LWS_EXTERN int
795 lws_add_http_header_by_name(struct libwebsocket_context *context,
796 struct libwebsocket *wsi,
797 const unsigned char *name,
798 const unsigned char *value,
803 Add a header like name: value in HTTP1.x
805 LWS_VISIBLE LWS_EXTERN int
806 lws_finalize_http_header(struct libwebsocket_context *context,
807 struct libwebsocket *wsi,
811 Finish off the headers, like add the extra \r\n in HTTP1.x
813 LWS_VISIBLE LWS_EXTERN int
814 lws_add_http_header_by_token(struct libwebsocket_context *context,
815 struct libwebsocket *wsi,
816 enum lws_token_indexes token,
817 const unsigned char *value,
822 Add a header by using a lws token as the name part. In HTTP2, this can be
823 compressed to one or two bytes.
829 protocols struct member no_buffer_all_partial_tx is removed. Under some
830 conditions like rewriting extension such as compression in use, the built-in
831 partial send buffering is the only way to deal with the problem, so turning
832 it off is deprecated.
838 HTTP2-related: API libwebsockets_serve_http_file() takes an extra parameter at
841 int other_headers_len)
843 If you are providing other headers, they must be generated using the new
844 HTTP-version-agnostic APIs, and you must provide the length of them using this
845 additional parameter.
847 struct lws_context_creation_info now has an additional member
848 SSL_CTX *provided_client_ssl_ctx you may set to an externally-initialized
849 SSL_CTX managed outside lws. Defaulting to zero keeps the existing behaviour of
850 lws managing the context, if you memset the struct to 0 or have as a filescope
851 initialized struct in bss, no need to change anything.
854 v1.3-chrome37-firefox30
855 =======================
858 CMakeLists.txt | 447 +++--
862 cmake/LibwebsocketsConfig.cmake.in | 17 +
863 cmake/LibwebsocketsConfigVersion.cmake.in | 11 +
864 config.h.cmake | 18 +
865 cross-ming.cmake | 31 +
866 cross-openwrt-makefile | 91 +
867 lib/client-handshake.c | 205 ++-
868 lib/client-parser.c | 58 +-
869 lib/client.c | 158 +-
870 lib/context.c | 341 ++++
871 lib/extension-deflate-frame.c | 2 +-
872 lib/extension.c | 178 ++
873 lib/handshake.c | 287 +---
874 lib/lextable.h | 338 ++++
876 lib/libwebsockets.c | 2089 +++--------------------
877 lib/libwebsockets.h | 253 ++-
878 lib/lws-plat-unix.c | 404 +++++
879 lib/lws-plat-win.c | 358 ++++
880 lib/minilex.c | 530 +++---
881 lib/output.c | 445 ++---
882 lib/parsers.c | 682 ++++----
883 lib/pollfd.c | 239 +++
884 lib/private-libwebsockets.h | 501 +++++-
885 lib/server-handshake.c | 274 +--
886 lib/server.c | 858 ++++++++--
887 lib/service.c | 517 ++++++
889 lib/ssl-http2.c | 78 +
890 lib/ssl.c | 571 +++++++
891 test-server/attack.sh | 101 +-
892 test-server/test-client.c | 9 +-
893 test-server/test-echo.c | 17 +-
894 test-server/test-fraggle.c | 7 -
895 test-server/test-ping.c | 12 +-
896 test-server/test-server.c | 330 ++--
897 test-server/test.html | 4 +-
898 win32port/client/client.vcxproj | 259 ---
899 win32port/client/client.vcxproj.filters | 39 -
900 .../libwebsocketswin32.vcxproj.filters | 93 -
901 win32port/server/server.vcxproj | 276 ---
902 win32port/server/server.vcxproj.filters | 51 -
903 win32port/win32helpers/gettimeofday.h | 59 +-
904 win32port/win32helpers/netdb.h | 1 -
905 win32port/win32helpers/strings.h | 0
906 win32port/win32helpers/sys/time.h | 1 -
907 win32port/win32helpers/unistd.h | 0
908 win32port/win32helpers/websock-w32.c | 104 --
909 win32port/win32helpers/websock-w32.h | 62 -
910 win32port/win32port.sln | 100 --
911 win32port/zlib/gzio.c | 3 +-
912 55 files changed, 6779 insertions(+), 5059 deletions(-)
918 POST method is supported
920 The protocol 0 / HTTP callback can now get two new kinds of callback,
921 LWS_CALLBACK_HTTP_BODY (in and len are a chunk of the body of the HTTP request)
922 and LWS_CALLBACK_HTTP_BODY_COMPLETION (the expected amount of body has arrived
923 and been passed to the user code already). These callbacks are used with the
924 post method (see the test server for details).
926 The period between the HTTP header completion and the completion of the body
927 processing is protected by a 5s timeout.
929 The chunks are stored in a malloc'd buffer of size protocols[0].rx_buffer_size.
932 New server option you can enable from user code
933 LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT allows non-SSL connections to
934 also be accepted on an SSL listening port. It's disabled unless you enable
938 Two new callbacks are added in protocols[0] that are optional for allowing
939 limited thread access to libwebsockets, LWS_CALLBACK_LOCK_POLL and
940 LWS_CALLBACK_UNLOCK_POLL.
942 If you use them, they protect internal and external poll list changes, but if
943 you want to use external thread access to libwebsocket_callback_on_writable()
944 you have to implement your locking here even if you don't use external
947 If you will use another thread for this, take a lot of care about managing
948 your list of live wsi by doing it from ESTABLISHED and CLOSED callbacks
949 (with your own locking).
951 If you configure cmake with -DLWS_WITH_LIBEV=1 then the code allowing the libev
952 eventloop instead of the default poll() one will also be compiled in. But to
953 use it, you must also set the LWS_SERVER_OPTION_LIBEV flag on the context
954 creation info struct options member.
956 IPV6 is supported and enabled by default except for Windows, you can disable
957 the support at build-time by giving -DLWS_IPV6=, and disable use of it even if
958 compiled in by making sure the flag LWS_SERVER_OPTION_DISABLE_IPV6 is set on
959 the context creation info struct options member.
961 You can give LWS_SERVER_OPTION_DISABLE_OS_CA_CERTS option flag to
962 guarantee the OS CAs will not be used, even if that support was selected at
965 Optional "token limits" may be enforced by setting the member "token_limits"
966 in struct lws_context_creation_info to point to a struct lws_token_limits.
967 NULL means no token limits used for compatibility.
973 Extra optional argument to libwebsockets_serve_http_file() allows injecion
974 of HTTP headers into the canned response. Eg, cookies may be added like
975 that without getting involved in having to send the header by hand.
977 A new info member http_proxy_address may be used at context creation time to
978 set the http proxy. If non-NULL, it overrides http_proxy environment var.
980 Cmake supports LWS_SSL_CLIENT_USE_OS_CA_CERTS defaulting to on, which gets
981 the client to use the OS CA Roots. If you're worried somebody with the
982 ability to forge for force creation of a client cert from the root CA in
983 your OS, you should disable this since your selfsigned $0 cert is a lot safer
987 v1.23-chrome32-firefox24
988 ========================
991 CMakeLists.txt | 573 ++++++++----
992 COPYING | 503 -----------
993 INSTALL | 365 --------
995 README.build | 371 ++------
996 README.coding | 63 ++
997 autogen.sh | 1578 ---------------------------------
999 cmake/FindGit.cmake | 163 ++++
1000 cmake/FindOpenSSLbins.cmake | 15 +-
1001 cmake/UseRPMTools.cmake | 176 ++++
1002 config.h.cmake | 25 +-
1003 configure.ac | 226 -----
1004 cross-arm-linux-gnueabihf.cmake | 28 +
1005 lib/Makefile.am | 89 --
1006 lib/base64-decode.c | 98 +-
1007 lib/client-handshake.c | 123 ++-
1008 lib/client-parser.c | 19 +-
1009 lib/client.c | 145 ++-
1010 lib/daemonize.c | 4 +-
1011 lib/extension.c | 2 +-
1012 lib/getifaddrs.h | 4 +-
1013 lib/handshake.c | 76 +-
1014 lib/libwebsockets.c | 491 ++++++----
1015 lib/libwebsockets.h | 164 ++--
1016 lib/output.c | 214 ++++-
1017 lib/parsers.c | 102 +--
1018 lib/private-libwebsockets.h | 66 +-
1019 lib/server-handshake.c | 5 +-
1020 lib/server.c | 29 +-
1022 libwebsockets-api-doc.html | 249 +++---
1023 libwebsockets.pc.in | 11 -
1024 libwebsockets.spec | 14 +-
1026 scripts/FindLibWebSockets.cmake | 33 +
1027 scripts/kernel-doc | 1 +
1028 test-server/Makefile.am | 131 ---
1029 test-server/leaf.jpg | Bin 0 -> 2477518 bytes
1030 test-server/test-client.c | 78 +-
1031 test-server/test-echo.c | 33 +-
1032 test-server/test-fraggle.c | 26 +-
1033 test-server/test-ping.c | 15 +-
1034 test-server/test-server.c | 197 +++-
1035 test-server/test.html | 5 +-
1036 win32port/win32helpers/gettimeofday.c | 74 +-
1037 win32port/win32helpers/websock-w32.h | 6 +-
1038 48 files changed, 2493 insertions(+), 4212 deletions(-)
1044 - You can now call libwebsocket_callback_on_writable() on http connectons,
1045 and get a LWS_CALLBACK_HTTP_WRITEABLE callback, the same way you can
1046 regulate writes with a websocket protocol connection.
1048 - A new member in the context creation parameter struct "ssl_cipher_list" is
1049 added, replacing CIPHERS_LIST_STRING. NULL means use the ssl library
1050 default list of ciphers.
1052 - Not really an api addition, but libwebsocket_service_fd() will now zero
1053 the revents field of the pollfd it was called with if it handled the
1054 descriptor. So you can tell if it is a non-lws fd by checking revents
1055 after the service call... if it's still nonzero, the descriptor
1056 belongs to you and you need to take care of it.
1058 - libwebsocket_rx_flow_allow_all_protocol(protocol) will unthrottle all
1059 connections with the established protocol. It's designed to be
1060 called from user server code when it sees it can accept more input
1061 and may have throttled connections using the server rx flow apis
1062 while it was unable to accept any other input The user server code
1063 then does not have to try to track while connections it choked, this
1064 will free up all of them in one call.
1066 - there's a new, optional callback LWS_CALLBACK_CLOSED_HTTP which gets
1067 called when an HTTP protocol socket closes
1069 - for LWS_CALLBACK_FILTER_PROTOCOL_CONNECTION callback, the user_space alloc
1070 has already been done before the callback happens. That means we can
1071 use the user parameter to the callback to contain the user pointer, and
1072 move the protocol name to the "in" parameter. The docs for this
1073 callback are also updated to reflect how to check headers in there.
1075 - libwebsocket_client_connect() is now properly nonblocking and async. See
1076 README.coding and test-client.c for information on the callbacks you
1077 can rely on controlling the async connection period with.
1079 - if your OS does not support the http_proxy environment variable convention
1080 (eg, reportedly OSX), you can use a new api libwebsocket_set_proxy()
1081 to set the proxy details in between context creation and the connection
1082 action. For OSes that support http_proxy, that's used automatically.
1087 - the external poll callbacks now get the socket descriptor coming from the
1088 "in" parameter. The user parameter provides the user_space for the
1089 wsi as it normally does on the other callbacks.
1090 LWS_CALLBACK_FILTER_NETWORK_CONNECTION also has the socket descriptor
1091 delivered by @in now instead of @user.
1093 - libwebsocket_write() now returns -1 for error, or the amount of data
1094 actually accepted for send. Under load, the OS may signal it is
1095 ready to send new data on the socket, but have only a restricted
1096 amount of memory to buffer the packet compared to usual.
1102 - libwebsocket_ensure_user_space() is removed from the public api, if you
1103 were using it to get user_space, you need to adapt your code to only
1104 use user_space inside the user callback.
1106 - CIPHERS_LIST_STRING is removed
1108 - autotools build has been removed. See README.build for info on how to
1109 use CMake for your platform
1112 v1.21-chrome26-firefox18
1113 ========================
1115 - Fixes buffer overflow bug in max frame size handling if you used the
1116 default protocol buffer size. If you declared rx_buffer_size in your
1117 protocol, which is recommended anyway, your code was unaffected.
1119 v1.2-chrome26-firefox18
1120 =======================
1126 CMakeLists.txt | 544 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1127 LICENSE | 526 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1130 README.build | 258 ++++++++++++++++++++++++++++++++-----
1131 README.coding | 52 ++++++++
1132 changelog | 136 ++++++++++++++++++++
1133 cmake/FindOpenSSLbins.cmake | 33 +++++
1134 config.h.cmake | 173 +++++++++++++++++++++++++
1135 configure.ac | 22 +++-
1136 lib/Makefile.am | 20 ++-
1137 lib/base64-decode.c | 2 +-
1138 lib/client-handshake.c | 190 +++++++++++-----------------
1139 lib/client-parser.c | 88 +++++++------
1140 lib/client.c | 384 ++++++++++++++++++++++++++++++-------------------------
1141 lib/daemonize.c | 32 +++--
1142 lib/extension-deflate-frame.c | 58 +++++----
1143 lib/extension-deflate-stream.c | 19 ++-
1144 lib/extension-deflate-stream.h | 4 +-
1145 lib/extension.c | 11 +-
1146 lib/getifaddrs.c | 315 +++++++++++++++++++++++-----------------------
1147 lib/getifaddrs.h | 30 ++---
1148 lib/handshake.c | 124 +++++++++++-------
1149 lib/libwebsockets.c | 736 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------
1150 lib/libwebsockets.h | 237 ++++++++++++++++++++++------------
1151 lib/output.c | 192 +++++++++++-----------------
1152 lib/parsers.c | 966 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------
1153 lib/private-libwebsockets.h | 225 +++++++++++++++++++++------------
1154 lib/server-handshake.c | 82 ++++++------
1155 lib/server.c | 96 +++++++-------
1156 libwebsockets-api-doc.html | 189 ++++++++++++++++++----------
1157 libwebsockets.spec | 17 +--
1158 test-server/attack.sh | 148 ++++++++++++++++++++++
1159 test-server/test-client.c | 125 +++++++++---------
1160 test-server/test-echo.c | 31 +++--
1161 test-server/test-fraggle.c | 32 ++---
1162 test-server/test-ping.c | 52 ++++----
1163 test-server/test-server.c | 129 ++++++++++++-------
1164 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj | 279 ----------------------------------------
1165 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj.filters | 23 +++-
1166 41 files changed, 4398 insertions(+), 2219 deletions(-)
1172 - lws_get_library_version() returns a const char * with a string like
1173 "1.1 9e7f737", representing the library version from configure.ac
1174 and the git HEAD hash the library was built from
1176 - TCP Keepalive can now optionally be applied to all lws sockets, on Linux
1177 also with controllable timeout, number of probes and probe interval.
1178 (On BSD type OS, you can only use system default settings for the
1179 timing and retries, although enabling it is supported by setting
1180 ka_time to nonzero, the exact value has no meaning.)
1181 This enables detection of idle connections which are logically okay,
1182 but are in fact dead, due to network connectivity issues at the server,
1183 client, or any intermediary. By default it's not enabled, but you
1184 can enable it by setting a non-zero timeout (in seconds) at the new
1185 ka_time member at context creation time.
1187 - Two new optional user callbacks added, LWS_CALLBACK_PROTOCOL_DESTROY which
1188 is called one-time per protocol as the context is being destroyed, and
1189 LWS_CALLBACK_PROTOCOL_INIT which is called when the context is created
1190 and the protocols are added, again it's a one-time affair.
1191 This lets you manage per-protocol allocations properly including
1192 cleaning up after yourself when the server goes down.
1197 - libwebsocket_create_context() has changed from taking a ton of parameters
1198 to just taking a pointer to a struct containing the parameters. The
1199 struct lws_context_creation_info is in libwebsockets.h, the members
1200 are in the same order as when they were parameters to the call
1201 previously. The test apps are all updated accordingly so you can
1202 see example code there.
1204 - Header tokens are now deleted after the websocket connection is
1205 established. Not just the header data is saved, but the pointer and
1206 length array is also removed from (union) scope saving several hundred
1207 bytes per connection once it is established
1209 - struct libwebsocket_protocols has a new member rx_buffer_size, this
1210 controls rx buffer size per connection of that protocol now. Sources
1211 for apps built against older versions of the library won't declare
1212 this in their protocols, defaulting it to 0. Zero buffer is legal,
1213 it causes a default buffer to be allocated (currently 4096)
1215 If you want to receive only atomic frames in your user callback, you
1216 should set this to greater than your largest frame size. If a frame
1217 comes that exceeds that, no error occurs but the callback happens as
1218 soon as the buffer limit is reached, and again if it is reached again
1219 or the frame completes. You can detect that has happened by seeing
1220 there is still frame content pending using
1221 libwebsockets_remaining_packet_payload()
1223 By correctly setting this, you can save a lot of memory when your
1224 protocol has small frames (see the test server and client sources).
1226 - LWS_MAX_HEADER_LEN now defaults to 1024 and is the total amount of known
1227 header payload lws can cope with, that includes the GET URL, origin
1228 etc. Headers not understood by lws are ignored and their payload
1229 not included in this.
1235 - The configuration-time option MAX_USER_RX_BUFFER has been replaced by a
1236 buffer size chosen per-protocol. For compatibility, there's a default
1237 of 4096 rx buffer, but user code should set the appropriate size for
1238 the protocol frames.
1240 - LWS_INITIAL_HDR_ALLOC and LWS_ADDITIONAL_HDR_ALLOC are no longer needed
1241 and have been removed. There's a new header management scheme that
1242 handles them in a much more compact way.
1244 - libwebsockets_hangup_on_client() is removed. If you want to close the
1245 connection you must do so from the user callback and by returning
1248 - libwebsocket_close_and_free_session() is now private to the library code
1249 only and not exposed for user code. If you want to close the
1250 connection, you must do so from the user callback by returning -1
1257 - Cmake project file added, aimed initially at Windows support: this replaces
1258 the visual studio project files that were in the tree until now.
1260 - CyaSSL now supported in place of OpenSSL (--use-cyassl on configure)
1262 - PATH_MAX or MAX_PATH no longer needed
1264 - cutomizable frame rx buffer size by protocol
1266 - optional TCP keepalive so dead peers can be detected, can be enabled at
1267 context-creation time
1269 - valgrind-clean: no SSL or CyaSSL: completely clean. With OpenSSL, 88 bytes
1270 lost at OpenSSL library init and symptomless reports of uninitialized
1271 memory usage... seems to be a known and ignored problem at OpenSSL
1273 - By default debug is enabled and the library is built for -O0 -g to faclitate
1274 that. Use --disable-debug configure option to build instead with -O4
1275 and no -g (debug info), obviously providing best performance and
1276 reduced binary size.
1278 - 1.0 introduced some code to try to not deflate small frames, however this
1279 seems to break when confronted with a mixture of frames above and
1280 below the threshold, so it's removed. Veto the compression extension
1281 in your user callback if you will typically have very small frames.
1283 - There are many memory usage improvements, both a reduction in malloc/
1284 realloc and architectural changes. A websocket connection now
1285 consumes only 296 bytes with SSL or 272 bytes without on x86_64,
1286 during header processing an additional 1262 bytes is allocated in a
1287 single malloc, but is freed when the websocket connection starts.
1288 The RX frame buffer defined by the protocol in user
1289 code is also allocated per connection, this represents the largest
1290 frame you can receive atomically in that protocol.
1292 - On ARM9 build, just http+ws server no extensions or ssl, <12Kbytes .text
1293 and 112 bytes per connection (+1328 only during header processing)
1296 v1.1-chrome26-firefox18
1297 =======================
1303 README-test-server | 291 ---
1304 README.build | 239 ++
1305 README.coding | 138 ++
1307 README.test-apps | 272 +++
1308 configure.ac | 116 +-
1309 lib/Makefile.am | 55 +-
1310 lib/base64-decode.c | 5 +-
1311 lib/client-handshake.c | 121 +-
1312 lib/client-parser.c | 394 ++++
1313 lib/client.c | 807 +++++++
1314 lib/daemonize.c | 212 ++
1315 lib/extension-deflate-frame.c | 132 +-
1316 lib/extension-deflate-stream.c | 12 +-
1317 lib/extension-x-google-mux.c | 1223 ----------
1318 lib/extension-x-google-mux.h | 96 -
1319 lib/extension.c | 8 -
1320 lib/getifaddrs.c | 271 +++
1321 lib/getifaddrs.h | 76 +
1322 lib/handshake.c | 582 +----
1323 lib/libwebsockets.c | 2493 ++++++---------------
1324 lib/libwebsockets.h | 115 +-
1326 lib/minilex.c | 440 ++++
1327 lib/output.c | 628 ++++++
1328 lib/parsers.c | 2016 +++++------------
1329 lib/private-libwebsockets.h | 284 +--
1330 lib/server-handshake.c | 275 +++
1331 lib/server.c | 377 ++++
1332 libwebsockets-api-doc.html | 300 +--
1334 test-server/Makefile.am | 111 +-
1335 test-server/libwebsockets.org-logo.png | Bin 0 -> 7029 bytes
1336 test-server/test-client.c | 45 +-
1337 test-server/test-echo.c | 330 +++
1338 test-server/test-fraggle.c | 20 +-
1339 test-server/test-ping.c | 22 +-
1340 test-server/test-server-extpoll.c | 554 -----
1341 test-server/test-server.c | 349 ++-
1342 test-server/test.html | 3 +-
1343 win32port/zlib/ZLib.vcxproj | 749 ++++---
1344 win32port/zlib/ZLib.vcxproj.filters | 188 +-
1345 win32port/zlib/adler32.c | 348 ++-
1346 win32port/zlib/compress.c | 160 +-
1347 win32port/zlib/crc32.c | 867 ++++----
1348 win32port/zlib/crc32.h | 882 ++++----
1349 win32port/zlib/deflate.c | 3799 +++++++++++++++-----------------
1350 win32port/zlib/deflate.h | 688 +++---
1351 win32port/zlib/gzclose.c | 50 +-
1352 win32port/zlib/gzguts.h | 325 ++-
1353 win32port/zlib/gzlib.c | 1157 +++++-----
1354 win32port/zlib/gzread.c | 1242 ++++++-----
1355 win32port/zlib/gzwrite.c | 1096 +++++----
1356 win32port/zlib/infback.c | 1272 ++++++-----
1357 win32port/zlib/inffast.c | 680 +++---
1358 win32port/zlib/inffast.h | 22 +-
1359 win32port/zlib/inffixed.h | 188 +-
1360 win32port/zlib/inflate.c | 2976 +++++++++++++------------
1361 win32port/zlib/inflate.h | 244 +-
1362 win32port/zlib/inftrees.c | 636 +++---
1363 win32port/zlib/inftrees.h | 124 +-
1364 win32port/zlib/trees.c | 2468 +++++++++++----------
1365 win32port/zlib/trees.h | 256 +--
1366 win32port/zlib/uncompr.c | 118 +-
1367 win32port/zlib/zconf.h | 934 ++++----
1368 win32port/zlib/zlib.h | 3357 ++++++++++++++--------------
1369 win32port/zlib/zutil.c | 642 +++---
1370 win32port/zlib/zutil.h | 526 ++---
1371 69 files changed, 19556 insertions(+), 20145 deletions(-)
1376 - libwebsockets_serve_http_file() now takes a context as first argument
1378 - libwebsockets_get_peer_addresses() now takes a context and wsi as first
1385 - lwsl_...() logging apis, default to stderr but retargetable by user code;
1386 may be used also by user code
1388 - lws_set_log_level() set which logging apis are able to emit (defaults to
1389 notice, warn, err severities), optionally set the emit callback
1391 - lwsl_emit_syslog() helper callback emits to syslog
1393 - lws_daemonize() helper code that forks the app into a headless daemon
1394 properly, maintains a lock file with pid in suitable for sysvinit etc to
1397 - LWS_CALLBACK_HTTP_FILE_COMPLETION callback added since http file
1398 transfer is now asynchronous (see test server code)
1400 - lws_frame_is_binary() from a wsi pointer, let you know if the received
1401 data was sent in BINARY mode
1407 - libwebsockets_fork_service_loop() - no longer supported (had intractable problems)
1408 arrange your code to act from the user callback instead from same
1409 process context as the service loop
1411 - libwebsockets_broadcast() - use libwebsocket_callback_on_writable[_all_protocol]()
1412 instead from same process context as the service loop. See the test apps
1415 - x-google-mux() removed until someone wants it
1417 - pre -v13 (ancient) protocol support removed
1423 - echo test server and client compatible with echo.websocket.org added
1425 - many new configure options (see README.build) to reduce footprint of the
1426 library to what you actually need, eg, --without-client and
1429 - http + websocket server can build to as little as 12K .text for ARM
1431 - no more MAX_CLIENTS limitation; adapts to support the max number of fds
1432 allowed to the process by ulimit, defaults to 1024 on Fedora and
1433 Ubuntu. Use ulimit to control this without needing to configure
1434 the library. Code here is smaller and faster.
1436 - adaptive ratio of listen socket to connection socket service allows
1437 good behaviour under Apache ab test load. Tested with thousands
1438 of simultaneous connections
1440 - reduction in per-connection memory footprint by moving to a union to hold
1441 mutually-exclusive state for the connection
1443 - robustness: Out of Memory taken care of for all allocation code now
1445 - internal getifaddrs option if your toolchain lacks it (some uclibc)
1447 - configurable memory limit for deflate operations
1449 - improvements in SSL code nonblocking operation, possible hang solved,
1450 some SSL operations broken down into pollable states so there is
1451 no library blocking, timeout coverage for SSL_connect
1453 - extpoll test server merged into single test server source
1455 - robustness: library should deal with all recoverable socket conditions
1457 - rx flowcontrol for backpressure notification fixed and implmeneted
1458 correctly in the test server
1460 - optimal lexical parser added for header processing; all headers in a
1461 single 276-byte state table
1463 - latency tracking api added (configure --with-latency)
1465 - Improved in-tree documentation, REAME.build, README.coding,
1466 README.test-apps, changelog
1471 v1.0-chrome25-firefox17 (6cd1ea9b005933f)