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
45 1) MINOR test-server gained some new switches
47 -C <file> use external SSL cert file
48 -K <file> use external SSL key file
49 -A <file> use external SSL CA cert file
51 -u <uid> set effective uid
52 -g <gid> set effective gid
54 together you can use them like this to have the test-server work with the
55 usual purchased SSL certs from an official CA.
57 --ssl -C your.crt -K your.key -A your.cer -u 99 -g 99
59 2) MINOR the OpenSSL magic to setup ECDH cipher usage is implemented in the
60 library, and the ciphers restricted to use ECDH only.
61 Using this, the lws test server can score an A at SSLLABS test
63 3) MINOR STS (SSL always) header is added to the test server if you use --ssl. With
64 that, we score A+ at SSLLABS test
66 4) MINOR daemonize function (disabled at cmake by default) is updated to work
69 5) MINOR example systemd .service file now provided for test server
70 (not installed by default)
72 6) test server html is updated with tabs and a new live server monitoring
73 feature. Input sanitization added to the js.
75 7) client connections attempted when no ah is free no longer fail, they are
76 just deferred until an ah becomes available.
78 8) The test client pays attention to if you give it an http:/ or https://
79 protocol string to its argument in URL format. If so, it stays in http[s]
80 client mode and doesn't upgrade to ws[s], allowing you to do generic http client
87 1) MINOR APIBREAK There's a new member in struct lws_context_creation_info, ecdh_curve,
88 which lets you set the name of the ECDH curve OpenSSL should use. By
89 default (if you leave ecdh_curve NULL) it will use "prime256v1"
91 2) MINOR NEWAPI It was already possible to adopt a foreign socket that had not
92 been read from using lws_adopt_socket() since v1.7. Now you can adopt a
93 partially-used socket if you don't need SSL, by passing it what you read
94 so it can drain that before reading from the socket.
96 LWS_VISIBLE LWS_EXTERN struct lws *
97 lws_adopt_socket_readbuf(struct lws_context *context, lws_sockfd_type accept_fd,
98 const char *readbuf, size_t len);
100 3) MINOR NEWAPI CGI type "network io" subprocess execution is now possible from
103 LWS_VISIBLE LWS_EXTERN int
104 lws_cgi(struct lws *wsi, char * const *exec_array, int timeout_secs);
106 LWS_VISIBLE LWS_EXTERN int
107 lws_cgi_kill(struct lws *wsi);
109 To use it, you must first set the cmake option
111 $ cmake .. -DLWS_WITH_CGI=1
113 See test-server-http.c and test server path
115 http://localhost:7681/cgitest
117 stdin gets http body, you can test it with wget
119 $ echo hello > hello.txt
120 $ wget http://localhost:7681/cgitest --post-file=hello.txt -O- --quiet
124 4) There is a helper api for forming logging timestamps
127 lwsl_timestamp(int level, char *p, int len)
129 this generates this kind of timestamp for use as logging preamble
131 lwsts[13116]: [2016/01/25 14:52:52:8386] NOTICE: Initial logging level 7
133 5) struct lws_client_connect_info has a new member
137 If it's NULL, then everything happens as before, lws_client_connect_via_info()
138 makes a ws or wss connection to the address given.
140 If you set method to a valid http method like "GET", though, then this method
141 is used and the connection remains in http[s], it's not upgraded to ws[s].
143 So with this, you can perform http[s] client operations as well as ws[s] ones.
145 There are 4 new related callbacks
147 LWS_CALLBACK_ESTABLISHED_CLIENT_HTTP = 44,
148 LWS_CALLBACK_CLOSED_CLIENT_HTTP = 45,
149 LWS_CALLBACK_RECEIVE_CLIENT_HTTP = 46,
150 LWS_CALLBACK_COMPLETED_CLIENT_HTTP = 47,
159 1) There is now a "permessage-deflate" / RFC7692 implementation. It's very
160 similar to "deflate-frame" we have offered for a long while; deflate-frame is
161 now provided as an alias of permessage-deflate.
163 The main differences are that the new permessage-deflate implementation:
165 - properly performs streaming respecting input and output buffer limits. The
166 old deflate-frame implementation could only work on complete deflate input
167 and produce complete inflate output for each frame. The new implementation
168 only mallocs buffers at initialization.
170 - goes around the event loop after each input package is processed allowing
171 interleaved output processing. The RX flow control api can be used to
172 force compressed input processing to match the rate of compressed output
173 processing (test--echo shows an example of how to do this).
175 - when being "deflate-frame" for compatibility he uses the same default zlib
176 settings as the old "deflate-frame", but instead of exponentially increasing
177 malloc allocations until the whole output will fit, he observes the default
178 input and output chunking buffer sizes of "permessage-deflate", that's
179 1024 in and 1024 out at a time.
181 2) deflate-stream has been disabled for many versions (for over a year) and is
182 now removed. Browsers are now standardizing on "permessage-deflate" / RFC7692
184 3) struct lws_extension is simplified, and lws extensions now have a public
185 api (their callback) for use in user code to compose extensions and options
186 the user code wants. lws_get_internal_exts() is deprecated but kept around
187 as a NOP. The changes allow one extension implementation to go by different
188 names and allows the user client code to control option offers per-ext.
190 The test client and server are updated to use the new way. If you use
191 the old way it should still work, but extensions will be disabled until you
194 Extensions are now responsible for allocating and per-instance private struct
195 at instance construction time and freeing it when the instance is destroyed.
196 Not needing to know the size means the extension's struct can be opaque
203 1) The info struct gained three new members
205 - max_http_header_data: 0 for default (1024) or set the maximum amount of known
206 http header payload that lws can deal with. Payload in unknown http
207 headers is dropped silently. If for some reason you need to send huge
208 cookies or other HTTP-level headers, you can now increase this at context-
211 - max_http_header_pool: 0 for default (16) or set the maximum amount of http
212 headers that can be tracked by lws in this context. For the server, if
213 the header pool is completely in use then accepts on the listen socket
214 are disabled until one becomes free. For the client, if you simultaneously
215 have pending connects for more than this number of client connections,
216 additional connects will fail until some of the pending connections timeout
219 - timeout_secs: 0 for default (currently 20s), or set the library's
220 network activity timeout to the given number of seconds
222 HTTP header processing in lws only exists until just after the first main
223 callback after the HTTP handshake... for ws connections that is ESTABLISHED and
224 for HTTP connections the HTTP callback.
226 So these settings are not related to the maximum number of simultaneous
227 connections, but the number of HTTP handshakes that may be expected or ongoing,
228 or have just completed, at one time. The reason it's useful is it changes the
229 memory allocation for header processing to be one-time at context creation
230 instead of every time there is a new connection, and gives you control over
233 Setting max_http_header_pool to 1 is fine it will just queue incoming
234 connections before the accept as necessary, you can still have as many
235 simultaneous post-header connections as you like. Since the http header
236 processing is completed and the allocation released after ESTABLISHED or the
237 HTTP callback, even with a pool of 1 many connections can be handled rapidly.
239 2) There is a new callback that allows the user code to get acccess to the
240 optional close code + aux data that may have been sent by the peer.
242 LWS_CALLBACK_WS_PEER_INITIATED_CLOSE:
243 The peer has sent an unsolicited Close WS packet. @in and
244 @len are the optional close code (first 2 bytes, network
245 order) and the optional additional information which is not
246 defined in the standard, and may be a string or non-human-
248 If you return 0 lws will echo the close and then close the
249 connection. If you return nonzero lws will just close the
252 As usual not handling it does the right thing, if you're not interested in it
255 The test server has "open and close" testing buttons at the bottom, if you
256 open and close that connection, on close it will send a close code 3000 decimal
257 and the string "Bye!" as the aux data.
259 The test server dumb-increment callback handles this callback reason and prints
261 lwsts[15714]: LWS_CALLBACK_WS_PEER_INITIATED_CLOSE: len 6
262 lwsts[15714]: 0: 0x0B
263 lwsts[15714]: 1: 0xB8
264 lwsts[15714]: 2: 0x42
265 lwsts[15714]: 3: 0x79
266 lwsts[15714]: 4: 0x65
267 lwsts[15714]: 5: 0x21
269 3) There is a new API to allow the user code to control the content of the
270 close frame sent when about to return nonzero from the user callback to
271 indicate the connection should close.
274 * lws_close_reason - Set reason and aux data to send with Close packet
275 * If you are going to return nonzero from the callback
276 * requesting the connection to close, you can optionally
277 * call this to set the reason the peer will be told if
280 * @wsi: The websocket connection to set the close reason on
281 * @status: A valid close status from websocket standard
282 * @buf: NULL or buffer containing up to 124 bytes of auxiliary data
283 * @len: Length of data in @buf to send
285 LWS_VISIBLE LWS_EXTERN void
286 lws_close_reason(struct lws *wsi, enum lws_close_status status,
287 unsigned char *buf, size_t len);
289 An extra button is added to the "open and close" test server page that requests
290 that the test server close the connection from his end.
292 The test server code will do so by
294 lws_close_reason(wsi, LWS_CLOSE_STATUS_GOINGAWAY,
295 (unsigned char *)"seeya", 5);
298 The browser shows the close code and reason he received
300 websocket connection CLOSED, code: 1001, reason: seeya
302 4) There's a new context creation time option flag
304 LWS_SERVER_OPTION_VALIDATE_UTF8
306 if you set it in info->options, then TEXT and CLOSE frames will get checked to
307 confirm that they contain valid UTF-8. If they don't, the connection will get
310 5) ECDH Certs are now supported. Enable the CMake option
312 cmake .. -DLWS_SSL_SERVER_WITH_ECDH_CERT=1
314 **and** the info->options flag
316 LWS_SERVER_OPTION_SSL_ECDH
318 to build in support and select it at runtime.
320 6) There's a new api lws_parse_uri() that simplifies chopping up
321 https://xxx:yyy/zzz uris into parts nicely. The test client now uses this
322 to allow proper uris as well as the old address style.
324 7) SMP support is integrated into LWS without any internal threading. It's
325 very simple to use, libwebsockets-test-server-pthread shows how to do it,
326 use -j <n> argument there to control the number of service threads up to 32.
328 Two new members are added to the info struct
330 unsigned int count_threads;
331 unsigned int fd_limit_per_thread;
333 leave them at the default 0 to get the normal singlethreaded service loop.
335 Set count_threads to n to tell lws you will have n simultaneous service threads
336 operating on the context.
338 There is still a single listen socket on one port, no matter how many
341 When a connection is made, it is accepted by the service thread with the least
342 connections active to perform load balancing.
344 The user code is responsible for spawning n threads running the service loop
345 associated to a specific tsi (Thread Service Index, 0 .. n - 1). See
346 the libwebsockets-test-server-pthread for how to do.
348 If you leave fd_limit_per_thread at 0, then the process limit of fds is shared
349 between the service threads; if you process was allowed 1024 fds overall then
350 each thread is limited to 1024 / n.
352 You can set fd_limit_per_thread to a nonzero number to control this manually, eg
353 the overall supported fd limit is less than the process allowance.
355 You can control the context basic data allocation for multithreading from Cmake
356 using -DLWS_MAX_SMP=, if not given it's set to 32. The serv_buf allocation
357 for the threads (currently 4096) is made at runtime only for active threads.
359 Because lws will limit the requested number of actual threads supported
360 according to LWS_MAX_SMP, there is an api lws_get_count_threads(context) to
361 discover how many threads were actually allowed when the context was created.
363 It's required to implement locking in the user code in the same way that
364 libwebsockets-test-server-pthread does it, for the FD locking callbacks.
366 If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the
367 library. If more than 1, a small amount of pthread mutex code is built into
372 LWS_VISIBLE struct lws *
373 lws_adopt_socket(struct lws_context *context, lws_sockfd_type accept_fd)
375 allows foreign sockets accepted by non-lws code to be adopted by lws as if they
376 had just been accepted by lws' own listen socket.
378 9) X-Real-IP: header has been added as WSI_TOKEN_HTTP_X_REAL_IP
380 10) Libuv support is added, there are new related user apis
382 typedef void (lws_uv_signal_cb_t)(uv_loop_t *l, uv_signal_t *w, int revents);
384 LWS_VISIBLE LWS_EXTERN int
385 lws_uv_sigint_cfg(struct lws_context *context, int use_uv_sigint,
386 lws_uv_signal_cb_t *cb);
388 LWS_VISIBLE LWS_EXTERN int
389 lws_uv_initloop(struct lws_context *context, uv_loop_t *loop, int tsi);
392 lws_uv_sigint_cb(uv_loop_t *loop, uv_signal_t *watcher, int revents);
402 1) LWS_SEND_BUFFER_POST_PADDING is now 0 and deprecated. You can remove it; if
403 you still use it, obviously it does nothing. Old binary code with nonzero
404 LWS_SEND_BUFFER_POST_PADDING is perfectly compatible, the old code just
405 allocated a buffer bigger than the library is going to use.
407 The example apps no longer use LWS_SEND_BUFFER_POST_PADDING.
409 The only path who made use of it was sending with LWS_WRITE_CLOSE --->
411 2) Because of lws_close_reason() formalizing handling close frames,
412 LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send
413 close frames...close frame content should be managed using lws_close_reason()
416 3) We check for invalid CLOSE codes and complain about protocol violation in
417 our close code. But it changes little since we were in the middle of closing
420 4) zero-length RX frames and zero length TX frames are now allowed.
422 5) Pings and close used to be limited to 124 bytes, the correct limit is 125
423 so that is now also allowed.
425 6) LWS_PRE is provided as a synonym for LWS_SEND_BUFFER_PRE_PADDING, either is
428 7) There's generic support for RFC7462 style extension options built into the
429 library now. As a consequence, a field "options" is added to lws_extension.
430 It can be NULL if there are no options on the extension. Extension internal
431 info is part of the public abi because extensions may be implemented outside
434 8) WSI_TOKEN_PROXY enum was accidentally defined to collide with another token
435 of value 73. That's now corrected and WSI_TOKEN_PROXY moved to his own place at
438 9) With the addition of libuv support, libev is not the only event loop
439 library in town and his api names must be elaborated with _ev_
441 Callback typedef: lws_signal_cb ---> lws_ev_signal_cb_t
442 lws_sigint_cfg --> lws_ev_sigint_cfg
443 lws_initloop --> lws_ev_initloop
444 lws_sigint_cb --> lws_ev_sigint_cb
446 10) Libev support is made compatible with multithreaded service,
447 lws_ev_initloop (was lws_initloop) gets an extra argument for the
448 thread service index (use 0 if you will just have 1 service thread).
450 LWS_VISIBLE LWS_EXTERN int
451 lws_ev_initloop(struct lws_context *context, ev_loop_t *loop, int tsi);
454 v1.6.0-chrome48-firefox42
455 =======================
457 Major API improvements
458 ----------------------
460 v1.6.0 has many cleanups and improvements in the API. Although at first it
461 looks pretty drastic, user code will only need four actions to update it.
463 - Do the three search/replaces in your user code, /libwebsocket_/lws_/,
464 /libwebsockets_/lws_/, and /struct\ libwebsocket/struct\ lws/
466 - Remove the context parameter from your user callbacks
468 - Remove context as the first parameter from the "Eleven APIS" listed in the
469 User Api Changes section
471 - Add lws_get_context(wsi) as the first parameter on the "Three APIS" listed
472 in the User Api Changes section, and anywhere else you still need context
474 That's it... generally only a handful of the 14 affected APIs are actually in
475 use in your user code and you can find them quickest by compiling and visiting
476 the errors each in turn. And the end results are much cleaner, more
477 predictable and maintainable.
483 1) lws now exposes his internal platform file abstraction in a way that can be
484 both used by user code to make it platform-agnostic, and be overridden or
485 subclassed by user code. This allows things like handling the URI "directory
486 space" as a virtual filesystem that may or may not be backed by a regular
487 filesystem. One example use is serving files from inside large compressed
488 archive storage without having to unpack anything except the file being
491 The test server shows how to use it, basically the platform-specific part of
492 lws prepares a file operations structure that lives in the lws context.
494 Helpers are provided to also leverage these platform-independent file handling
497 static inline lws_filefd_type
498 lws_plat_file_open(struct lws *wsi, const char *filename,
499 unsigned long *filelen, int flags)
501 lws_plat_file_close(struct lws *wsi, lws_filefd_type fd)
503 static inline unsigned long
504 lws_plat_file_seek_cur(struct lws *wsi, lws_filefd_type fd, long offset)
507 lws_plat_file_read(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
508 unsigned char *buf, unsigned long len)
511 lws_plat_file_write(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
512 unsigned char *buf, unsigned long len)
514 The user code can also override or subclass the file operations, to either
515 wrap or replace them. An example is shown in test server.
517 A wsi can be associated with the file activity, allowing per-connection
518 authentication and state to be used when interpreting the file request.
520 2) A new API void * lws_wsi_user(struct lws *wsi) lets you get the pointer to
521 the user data associated with the wsi, just from the wsi.
523 3) URI argument handling. Libwebsockets parses and protects URI arguments
524 like test.html?arg1=1&arg2=2, it decodes %xx uriencoding format and reduces
525 path attacks like ../.../../etc/passwd so they cannot go behind the web
526 server's /. There is a list of confirmed attacks we're proof against in
527 ./test-server/attack.sh.
529 There is a new API lws_hdr_copy_fragment that should be used now to access
530 the URI arguments (it returns the fragments length)
532 while (lws_hdr_copy_fragment(wsi, buf, sizeof(buf),
533 WSI_TOKEN_HTTP_URI_ARGS, n) > 0) {
534 lwsl_info("URI Arg %d: %s\n", ++n, buf);
537 For the example above, calling with n=0 will return "arg1=1" and n=1 "arg2=2".
538 All legal uriencodings will have been reduced in those strings.
540 lws_hdr_copy_fragment() returns the length of the x=y fragment, so it's also
541 possible to deal with arguments containing %00. If you don't care about that,
542 the returned string has '\0' appended to simplify processing.
550 - lws_callback_on_writable_all_protocol(const struct lws_protocols *protocol)
551 - lws_callback_all_protocol(const struct lws_protocols *protocol)
552 - lws_rx_flow_allow_all_protocol(lws_rx_flow_allow_all_protocol)
554 Now take an additional pointer to the lws_context in their first argument.
556 The reason for this change is struct lws_protocols has been changed to remove
557 members that lws used for private storage: so the protocols struct in now
558 truly const and may be reused serially or simultaneously by different contexts.
562 LWS_VISIBLE LWS_EXTERN int
563 lws_add_http_header_by_name(struct lws_context *context,
565 const unsigned char *name,
566 const unsigned char *value,
570 LWS_VISIBLE LWS_EXTERN int
571 lws_finalize_http_header(struct lws_context *context,
575 LWS_VISIBLE LWS_EXTERN int
576 lws_add_http_header_by_token(struct lws_context *context,
578 enum lws_token_indexes token,
579 const unsigned char *value,
583 LWS_VISIBLE LWS_EXTERN int
584 lws_add_http_header_content_length(struct lws_context *context,
586 unsigned long content_length,
589 LWS_VISIBLE LWS_EXTERN int
590 lws_add_http_header_status(struct lws_context *context, struct lws *wsi,
591 unsigned int code, unsigned char **p,
594 LWS_VISIBLE LWS_EXTERN int
595 lws_serve_http_file(struct lws_context *context, struct lws *wsi,
596 const char *file, const char *content_type,
597 const char *other_headers, int other_headers_len);
598 LWS_VISIBLE LWS_EXTERN int
599 lws_serve_http_file_fragment(struct lws_context *context, struct lws *wsi);
601 LWS_VISIBLE LWS_EXTERN int
602 lws_return_http_status(struct lws_context *context, struct lws *wsi,
603 unsigned int code, const char *html_body);
605 LWS_VISIBLE LWS_EXTERN int
606 lws_callback_on_writable(const struct lws_context *context, struct lws *wsi);
608 LWS_VISIBLE LWS_EXTERN void
609 lws_get_peer_addresses(struct lws_context *context, struct lws *wsi,
610 lws_sockfd_type fd, char *name, int name_len,
611 char *rip, int rip_len);
613 LWS_VISIBLE LWS_EXTERN int
614 lws_read(struct lws_context *context, struct lws *wsi,
615 unsigned char *buf, size_t len);
617 no longer require their initial struct lws_context * parameter.
619 3) Several older apis start with libwebsocket_ or libwebsockets_ while newer ones
620 all begin lws_. These apis have been changed to all begin with lws_.
622 To convert, search-replace
624 - libwebsockets_/lws_
626 - struct\ libwebsocket/struct\ lws
628 4) context parameter removed from user callback.
630 Since almost all apis no longer need the context as a parameter, it's no longer
631 provided at the user callback directly.
633 However if you need it, for ALL callbacks wsi is valid and has a valid context
634 pointer you can recover using lws_get_context(wsi).
637 v1.5-chrome47-firefox41
638 =======================
643 LWS_CALLBACK_CLIENT_CONNECTION_ERROR may provide an error string if in is
644 non-NULL. If so, the string has length len.
646 LWS_SERVER_OPTION_PEER_CERT_NOT_REQUIRED is available to relax the requirement
647 for peer certs if you are using the option to require client certs.
649 LWS_WITHOUT_BUILTIN_SHA1 cmake option forces lws to use SHA1() defined
650 externally, eg, byOpenSSL, and disables build of libwebsockets_SHA1()
653 v1.4-chrome43-firefox36
654 =======================
659 There's a new member in the info struct used to control context creation,
660 ssl_private_key_password, which allows passing into lws the passphrase on
663 There's a new member in struct protocols, id, which is ignored by lws but can
664 be used by the user code to mark the selected protocol by user-defined version
665 or capabliity flag information, for the case multiple versions of a protocol are
668 int lws_is_ssl(wsi) added to allow user code to know if the connection was made
669 over ssl or not. If LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT is used, both
670 ssl and non-ssl connections are possible and may need to be treated differently
673 int lws_partial_buffered(wsi) added... should be checked after any
674 libwebsocket_write that will be followed by another libwebsocket_write inside
675 the same writeable callback. If set, you can't do any more writes until the
676 writeable callback is called again. If you only do one write per writeable callback,
679 HTTP2-related: HTTP2 changes how headers are handled, lws now has new version-
680 agnositic header creation APIs. These do the right thing depending on each
681 connection's HTTP version without the user code having to know or care, except
682 to make sure to use the new APIs for headers (test-server is updated to use
683 them already, so look there for examples)
685 The APIs "render" the headers into a user-provided buffer and bump *p as it
686 is used. If *p reaches end, then the APIs return nonzero for error.
688 LWS_VISIBLE LWS_EXTERN int
689 lws_add_http_header_status(struct libwebsocket_context *context,
690 struct libwebsocket *wsi,
695 Start a response header reporting status like 200, 500, etc
697 LWS_VISIBLE LWS_EXTERN int
698 lws_add_http_header_by_name(struct libwebsocket_context *context,
699 struct libwebsocket *wsi,
700 const unsigned char *name,
701 const unsigned char *value,
706 Add a header like name: value in HTTP1.x
708 LWS_VISIBLE LWS_EXTERN int
709 lws_finalize_http_header(struct libwebsocket_context *context,
710 struct libwebsocket *wsi,
714 Finish off the headers, like add the extra \r\n in HTTP1.x
716 LWS_VISIBLE LWS_EXTERN int
717 lws_add_http_header_by_token(struct libwebsocket_context *context,
718 struct libwebsocket *wsi,
719 enum lws_token_indexes token,
720 const unsigned char *value,
725 Add a header by using a lws token as the name part. In HTTP2, this can be
726 compressed to one or two bytes.
732 protocols struct member no_buffer_all_partial_tx is removed. Under some
733 conditions like rewriting extension such as compression in use, the built-in
734 partial send buffering is the only way to deal with the problem, so turning
735 it off is deprecated.
741 HTTP2-related: API libwebsockets_serve_http_file() takes an extra parameter at
744 int other_headers_len)
746 If you are providing other headers, they must be generated using the new
747 HTTP-version-agnostic APIs, and you must provide the length of them using this
748 additional parameter.
750 struct lws_context_creation_info now has an additional member
751 SSL_CTX *provided_client_ssl_ctx you may set to an externally-initialized
752 SSL_CTX managed outside lws. Defaulting to zero keeps the existing behaviour of
753 lws managing the context, if you memset the struct to 0 or have as a filescope
754 initialized struct in bss, no need to change anything.
757 v1.3-chrome37-firefox30
758 =======================
761 CMakeLists.txt | 447 +++--
765 cmake/LibwebsocketsConfig.cmake.in | 17 +
766 cmake/LibwebsocketsConfigVersion.cmake.in | 11 +
767 config.h.cmake | 18 +
768 cross-ming.cmake | 31 +
769 cross-openwrt-makefile | 91 +
770 lib/client-handshake.c | 205 ++-
771 lib/client-parser.c | 58 +-
772 lib/client.c | 158 +-
773 lib/context.c | 341 ++++
774 lib/extension-deflate-frame.c | 2 +-
775 lib/extension.c | 178 ++
776 lib/handshake.c | 287 +---
777 lib/lextable.h | 338 ++++
779 lib/libwebsockets.c | 2089 +++--------------------
780 lib/libwebsockets.h | 253 ++-
781 lib/lws-plat-unix.c | 404 +++++
782 lib/lws-plat-win.c | 358 ++++
783 lib/minilex.c | 530 +++---
784 lib/output.c | 445 ++---
785 lib/parsers.c | 682 ++++----
786 lib/pollfd.c | 239 +++
787 lib/private-libwebsockets.h | 501 +++++-
788 lib/server-handshake.c | 274 +--
789 lib/server.c | 858 ++++++++--
790 lib/service.c | 517 ++++++
792 lib/ssl-http2.c | 78 +
793 lib/ssl.c | 571 +++++++
794 test-server/attack.sh | 101 +-
795 test-server/test-client.c | 9 +-
796 test-server/test-echo.c | 17 +-
797 test-server/test-fraggle.c | 7 -
798 test-server/test-ping.c | 12 +-
799 test-server/test-server.c | 330 ++--
800 test-server/test.html | 4 +-
801 win32port/client/client.vcxproj | 259 ---
802 win32port/client/client.vcxproj.filters | 39 -
803 .../libwebsocketswin32.vcxproj.filters | 93 -
804 win32port/server/server.vcxproj | 276 ---
805 win32port/server/server.vcxproj.filters | 51 -
806 win32port/win32helpers/gettimeofday.h | 59 +-
807 win32port/win32helpers/netdb.h | 1 -
808 win32port/win32helpers/strings.h | 0
809 win32port/win32helpers/sys/time.h | 1 -
810 win32port/win32helpers/unistd.h | 0
811 win32port/win32helpers/websock-w32.c | 104 --
812 win32port/win32helpers/websock-w32.h | 62 -
813 win32port/win32port.sln | 100 --
814 win32port/zlib/gzio.c | 3 +-
815 55 files changed, 6779 insertions(+), 5059 deletions(-)
821 POST method is supported
823 The protocol 0 / HTTP callback can now get two new kinds of callback,
824 LWS_CALLBACK_HTTP_BODY (in and len are a chunk of the body of the HTTP request)
825 and LWS_CALLBACK_HTTP_BODY_COMPLETION (the expected amount of body has arrived
826 and been passed to the user code already). These callbacks are used with the
827 post method (see the test server for details).
829 The period between the HTTP header completion and the completion of the body
830 processing is protected by a 5s timeout.
832 The chunks are stored in a malloc'd buffer of size protocols[0].rx_buffer_size.
835 New server option you can enable from user code
836 LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT allows non-SSL connections to
837 also be accepted on an SSL listening port. It's disabled unless you enable
841 Two new callbacks are added in protocols[0] that are optional for allowing
842 limited thread access to libwebsockets, LWS_CALLBACK_LOCK_POLL and
843 LWS_CALLBACK_UNLOCK_POLL.
845 If you use them, they protect internal and external poll list changes, but if
846 you want to use external thread access to libwebsocket_callback_on_writable()
847 you have to implement your locking here even if you don't use external
850 If you will use another thread for this, take a lot of care about managing
851 your list of live wsi by doing it from ESTABLISHED and CLOSED callbacks
852 (with your own locking).
854 If you configure cmake with -DLWS_WITH_LIBEV=1 then the code allowing the libev
855 eventloop instead of the default poll() one will also be compiled in. But to
856 use it, you must also set the LWS_SERVER_OPTION_LIBEV flag on the context
857 creation info struct options member.
859 IPV6 is supported and enabled by default except for Windows, you can disable
860 the support at build-time by giving -DLWS_IPV6=, and disable use of it even if
861 compiled in by making sure the flag LWS_SERVER_OPTION_DISABLE_IPV6 is set on
862 the context creation info struct options member.
864 You can give LWS_SERVER_OPTION_DISABLE_OS_CA_CERTS option flag to
865 guarantee the OS CAs will not be used, even if that support was selected at
868 Optional "token limits" may be enforced by setting the member "token_limits"
869 in struct lws_context_creation_info to point to a struct lws_token_limits.
870 NULL means no token limits used for compatibility.
876 Extra optional argument to libwebsockets_serve_http_file() allows injecion
877 of HTTP headers into the canned response. Eg, cookies may be added like
878 that without getting involved in having to send the header by hand.
880 A new info member http_proxy_address may be used at context creation time to
881 set the http proxy. If non-NULL, it overrides http_proxy environment var.
883 Cmake supports LWS_SSL_CLIENT_USE_OS_CA_CERTS defaulting to on, which gets
884 the client to use the OS CA Roots. If you're worried somebody with the
885 ability to forge for force creation of a client cert from the root CA in
886 your OS, you should disable this since your selfsigned $0 cert is a lot safer
890 v1.23-chrome32-firefox24
891 ========================
894 CMakeLists.txt | 573 ++++++++----
895 COPYING | 503 -----------
896 INSTALL | 365 --------
898 README.build | 371 ++------
899 README.coding | 63 ++
900 autogen.sh | 1578 ---------------------------------
902 cmake/FindGit.cmake | 163 ++++
903 cmake/FindOpenSSLbins.cmake | 15 +-
904 cmake/UseRPMTools.cmake | 176 ++++
905 config.h.cmake | 25 +-
906 configure.ac | 226 -----
907 cross-arm-linux-gnueabihf.cmake | 28 +
908 lib/Makefile.am | 89 --
909 lib/base64-decode.c | 98 +-
910 lib/client-handshake.c | 123 ++-
911 lib/client-parser.c | 19 +-
912 lib/client.c | 145 ++-
913 lib/daemonize.c | 4 +-
914 lib/extension.c | 2 +-
915 lib/getifaddrs.h | 4 +-
916 lib/handshake.c | 76 +-
917 lib/libwebsockets.c | 491 ++++++----
918 lib/libwebsockets.h | 164 ++--
919 lib/output.c | 214 ++++-
920 lib/parsers.c | 102 +--
921 lib/private-libwebsockets.h | 66 +-
922 lib/server-handshake.c | 5 +-
925 libwebsockets-api-doc.html | 249 +++---
926 libwebsockets.pc.in | 11 -
927 libwebsockets.spec | 14 +-
929 scripts/FindLibWebSockets.cmake | 33 +
930 scripts/kernel-doc | 1 +
931 test-server/Makefile.am | 131 ---
932 test-server/leaf.jpg | Bin 0 -> 2477518 bytes
933 test-server/test-client.c | 78 +-
934 test-server/test-echo.c | 33 +-
935 test-server/test-fraggle.c | 26 +-
936 test-server/test-ping.c | 15 +-
937 test-server/test-server.c | 197 +++-
938 test-server/test.html | 5 +-
939 win32port/win32helpers/gettimeofday.c | 74 +-
940 win32port/win32helpers/websock-w32.h | 6 +-
941 48 files changed, 2493 insertions(+), 4212 deletions(-)
947 - You can now call libwebsocket_callback_on_writable() on http connectons,
948 and get a LWS_CALLBACK_HTTP_WRITEABLE callback, the same way you can
949 regulate writes with a websocket protocol connection.
951 - A new member in the context creation parameter struct "ssl_cipher_list" is
952 added, replacing CIPHERS_LIST_STRING. NULL means use the ssl library
953 default list of ciphers.
955 - Not really an api addition, but libwebsocket_service_fd() will now zero
956 the revents field of the pollfd it was called with if it handled the
957 descriptor. So you can tell if it is a non-lws fd by checking revents
958 after the service call... if it's still nonzero, the descriptor
959 belongs to you and you need to take care of it.
961 - libwebsocket_rx_flow_allow_all_protocol(protocol) will unthrottle all
962 connections with the established protocol. It's designed to be
963 called from user server code when it sees it can accept more input
964 and may have throttled connections using the server rx flow apis
965 while it was unable to accept any other input The user server code
966 then does not have to try to track while connections it choked, this
967 will free up all of them in one call.
969 - there's a new, optional callback LWS_CALLBACK_CLOSED_HTTP which gets
970 called when an HTTP protocol socket closes
972 - for LWS_CALLBACK_FILTER_PROTOCOL_CONNECTION callback, the user_space alloc
973 has already been done before the callback happens. That means we can
974 use the user parameter to the callback to contain the user pointer, and
975 move the protocol name to the "in" parameter. The docs for this
976 callback are also updated to reflect how to check headers in there.
978 - libwebsocket_client_connect() is now properly nonblocking and async. See
979 README.coding and test-client.c for information on the callbacks you
980 can rely on controlling the async connection period with.
982 - if your OS does not support the http_proxy environment variable convention
983 (eg, reportedly OSX), you can use a new api libwebsocket_set_proxy()
984 to set the proxy details in between context creation and the connection
985 action. For OSes that support http_proxy, that's used automatically.
990 - the external poll callbacks now get the socket descriptor coming from the
991 "in" parameter. The user parameter provides the user_space for the
992 wsi as it normally does on the other callbacks.
993 LWS_CALLBACK_FILTER_NETWORK_CONNECTION also has the socket descriptor
994 delivered by @in now instead of @user.
996 - libwebsocket_write() now returns -1 for error, or the amount of data
997 actually accepted for send. Under load, the OS may signal it is
998 ready to send new data on the socket, but have only a restricted
999 amount of memory to buffer the packet compared to usual.
1005 - libwebsocket_ensure_user_space() is removed from the public api, if you
1006 were using it to get user_space, you need to adapt your code to only
1007 use user_space inside the user callback.
1009 - CIPHERS_LIST_STRING is removed
1011 - autotools build has been removed. See README.build for info on how to
1012 use CMake for your platform
1015 v1.21-chrome26-firefox18
1016 ========================
1018 - Fixes buffer overflow bug in max frame size handling if you used the
1019 default protocol buffer size. If you declared rx_buffer_size in your
1020 protocol, which is recommended anyway, your code was unaffected.
1022 v1.2-chrome26-firefox18
1023 =======================
1029 CMakeLists.txt | 544 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1030 LICENSE | 526 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1033 README.build | 258 ++++++++++++++++++++++++++++++++-----
1034 README.coding | 52 ++++++++
1035 changelog | 136 ++++++++++++++++++++
1036 cmake/FindOpenSSLbins.cmake | 33 +++++
1037 config.h.cmake | 173 +++++++++++++++++++++++++
1038 configure.ac | 22 +++-
1039 lib/Makefile.am | 20 ++-
1040 lib/base64-decode.c | 2 +-
1041 lib/client-handshake.c | 190 +++++++++++-----------------
1042 lib/client-parser.c | 88 +++++++------
1043 lib/client.c | 384 ++++++++++++++++++++++++++++++-------------------------
1044 lib/daemonize.c | 32 +++--
1045 lib/extension-deflate-frame.c | 58 +++++----
1046 lib/extension-deflate-stream.c | 19 ++-
1047 lib/extension-deflate-stream.h | 4 +-
1048 lib/extension.c | 11 +-
1049 lib/getifaddrs.c | 315 +++++++++++++++++++++++-----------------------
1050 lib/getifaddrs.h | 30 ++---
1051 lib/handshake.c | 124 +++++++++++-------
1052 lib/libwebsockets.c | 736 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------
1053 lib/libwebsockets.h | 237 ++++++++++++++++++++++------------
1054 lib/output.c | 192 +++++++++++-----------------
1055 lib/parsers.c | 966 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------
1056 lib/private-libwebsockets.h | 225 +++++++++++++++++++++------------
1057 lib/server-handshake.c | 82 ++++++------
1058 lib/server.c | 96 +++++++-------
1059 libwebsockets-api-doc.html | 189 ++++++++++++++++++----------
1060 libwebsockets.spec | 17 +--
1061 test-server/attack.sh | 148 ++++++++++++++++++++++
1062 test-server/test-client.c | 125 +++++++++---------
1063 test-server/test-echo.c | 31 +++--
1064 test-server/test-fraggle.c | 32 ++---
1065 test-server/test-ping.c | 52 ++++----
1066 test-server/test-server.c | 129 ++++++++++++-------
1067 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj | 279 ----------------------------------------
1068 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj.filters | 23 +++-
1069 41 files changed, 4398 insertions(+), 2219 deletions(-)
1075 - lws_get_library_version() returns a const char * with a string like
1076 "1.1 9e7f737", representing the library version from configure.ac
1077 and the git HEAD hash the library was built from
1079 - TCP Keepalive can now optionally be applied to all lws sockets, on Linux
1080 also with controllable timeout, number of probes and probe interval.
1081 (On BSD type OS, you can only use system default settings for the
1082 timing and retries, although enabling it is supported by setting
1083 ka_time to nonzero, the exact value has no meaning.)
1084 This enables detection of idle connections which are logically okay,
1085 but are in fact dead, due to network connectivity issues at the server,
1086 client, or any intermediary. By default it's not enabled, but you
1087 can enable it by setting a non-zero timeout (in seconds) at the new
1088 ka_time member at context creation time.
1090 - Two new optional user callbacks added, LWS_CALLBACK_PROTOCOL_DESTROY which
1091 is called one-time per protocol as the context is being destroyed, and
1092 LWS_CALLBACK_PROTOCOL_INIT which is called when the context is created
1093 and the protocols are added, again it's a one-time affair.
1094 This lets you manage per-protocol allocations properly including
1095 cleaning up after yourself when the server goes down.
1100 - libwebsocket_create_context() has changed from taking a ton of parameters
1101 to just taking a pointer to a struct containing the parameters. The
1102 struct lws_context_creation_info is in libwebsockets.h, the members
1103 are in the same order as when they were parameters to the call
1104 previously. The test apps are all updated accordingly so you can
1105 see example code there.
1107 - Header tokens are now deleted after the websocket connection is
1108 established. Not just the header data is saved, but the pointer and
1109 length array is also removed from (union) scope saving several hundred
1110 bytes per connection once it is established
1112 - struct libwebsocket_protocols has a new member rx_buffer_size, this
1113 controls rx buffer size per connection of that protocol now. Sources
1114 for apps built against older versions of the library won't declare
1115 this in their protocols, defaulting it to 0. Zero buffer is legal,
1116 it causes a default buffer to be allocated (currently 4096)
1118 If you want to receive only atomic frames in your user callback, you
1119 should set this to greater than your largest frame size. If a frame
1120 comes that exceeds that, no error occurs but the callback happens as
1121 soon as the buffer limit is reached, and again if it is reached again
1122 or the frame completes. You can detect that has happened by seeing
1123 there is still frame content pending using
1124 libwebsockets_remaining_packet_payload()
1126 By correctly setting this, you can save a lot of memory when your
1127 protocol has small frames (see the test server and client sources).
1129 - LWS_MAX_HEADER_LEN now defaults to 1024 and is the total amount of known
1130 header payload lws can cope with, that includes the GET URL, origin
1131 etc. Headers not understood by lws are ignored and their payload
1132 not included in this.
1138 - The configuration-time option MAX_USER_RX_BUFFER has been replaced by a
1139 buffer size chosen per-protocol. For compatibility, there's a default
1140 of 4096 rx buffer, but user code should set the appropriate size for
1141 the protocol frames.
1143 - LWS_INITIAL_HDR_ALLOC and LWS_ADDITIONAL_HDR_ALLOC are no longer needed
1144 and have been removed. There's a new header management scheme that
1145 handles them in a much more compact way.
1147 - libwebsockets_hangup_on_client() is removed. If you want to close the
1148 connection you must do so from the user callback and by returning
1151 - libwebsocket_close_and_free_session() is now private to the library code
1152 only and not exposed for user code. If you want to close the
1153 connection, you must do so from the user callback by returning -1
1160 - Cmake project file added, aimed initially at Windows support: this replaces
1161 the visual studio project files that were in the tree until now.
1163 - CyaSSL now supported in place of OpenSSL (--use-cyassl on configure)
1165 - PATH_MAX or MAX_PATH no longer needed
1167 - cutomizable frame rx buffer size by protocol
1169 - optional TCP keepalive so dead peers can be detected, can be enabled at
1170 context-creation time
1172 - valgrind-clean: no SSL or CyaSSL: completely clean. With OpenSSL, 88 bytes
1173 lost at OpenSSL library init and symptomless reports of uninitialized
1174 memory usage... seems to be a known and ignored problem at OpenSSL
1176 - By default debug is enabled and the library is built for -O0 -g to faclitate
1177 that. Use --disable-debug configure option to build instead with -O4
1178 and no -g (debug info), obviously providing best performance and
1179 reduced binary size.
1181 - 1.0 introduced some code to try to not deflate small frames, however this
1182 seems to break when confronted with a mixture of frames above and
1183 below the threshold, so it's removed. Veto the compression extension
1184 in your user callback if you will typically have very small frames.
1186 - There are many memory usage improvements, both a reduction in malloc/
1187 realloc and architectural changes. A websocket connection now
1188 consumes only 296 bytes with SSL or 272 bytes without on x86_64,
1189 during header processing an additional 1262 bytes is allocated in a
1190 single malloc, but is freed when the websocket connection starts.
1191 The RX frame buffer defined by the protocol in user
1192 code is also allocated per connection, this represents the largest
1193 frame you can receive atomically in that protocol.
1195 - On ARM9 build, just http+ws server no extensions or ssl, <12Kbytes .text
1196 and 112 bytes per connection (+1328 only during header processing)
1199 v1.1-chrome26-firefox18
1200 =======================
1206 README-test-server | 291 ---
1207 README.build | 239 ++
1208 README.coding | 138 ++
1210 README.test-apps | 272 +++
1211 configure.ac | 116 +-
1212 lib/Makefile.am | 55 +-
1213 lib/base64-decode.c | 5 +-
1214 lib/client-handshake.c | 121 +-
1215 lib/client-parser.c | 394 ++++
1216 lib/client.c | 807 +++++++
1217 lib/daemonize.c | 212 ++
1218 lib/extension-deflate-frame.c | 132 +-
1219 lib/extension-deflate-stream.c | 12 +-
1220 lib/extension-x-google-mux.c | 1223 ----------
1221 lib/extension-x-google-mux.h | 96 -
1222 lib/extension.c | 8 -
1223 lib/getifaddrs.c | 271 +++
1224 lib/getifaddrs.h | 76 +
1225 lib/handshake.c | 582 +----
1226 lib/libwebsockets.c | 2493 ++++++---------------
1227 lib/libwebsockets.h | 115 +-
1229 lib/minilex.c | 440 ++++
1230 lib/output.c | 628 ++++++
1231 lib/parsers.c | 2016 +++++------------
1232 lib/private-libwebsockets.h | 284 +--
1233 lib/server-handshake.c | 275 +++
1234 lib/server.c | 377 ++++
1235 libwebsockets-api-doc.html | 300 +--
1237 test-server/Makefile.am | 111 +-
1238 test-server/libwebsockets.org-logo.png | Bin 0 -> 7029 bytes
1239 test-server/test-client.c | 45 +-
1240 test-server/test-echo.c | 330 +++
1241 test-server/test-fraggle.c | 20 +-
1242 test-server/test-ping.c | 22 +-
1243 test-server/test-server-extpoll.c | 554 -----
1244 test-server/test-server.c | 349 ++-
1245 test-server/test.html | 3 +-
1246 win32port/zlib/ZLib.vcxproj | 749 ++++---
1247 win32port/zlib/ZLib.vcxproj.filters | 188 +-
1248 win32port/zlib/adler32.c | 348 ++-
1249 win32port/zlib/compress.c | 160 +-
1250 win32port/zlib/crc32.c | 867 ++++----
1251 win32port/zlib/crc32.h | 882 ++++----
1252 win32port/zlib/deflate.c | 3799 +++++++++++++++-----------------
1253 win32port/zlib/deflate.h | 688 +++---
1254 win32port/zlib/gzclose.c | 50 +-
1255 win32port/zlib/gzguts.h | 325 ++-
1256 win32port/zlib/gzlib.c | 1157 +++++-----
1257 win32port/zlib/gzread.c | 1242 ++++++-----
1258 win32port/zlib/gzwrite.c | 1096 +++++----
1259 win32port/zlib/infback.c | 1272 ++++++-----
1260 win32port/zlib/inffast.c | 680 +++---
1261 win32port/zlib/inffast.h | 22 +-
1262 win32port/zlib/inffixed.h | 188 +-
1263 win32port/zlib/inflate.c | 2976 +++++++++++++------------
1264 win32port/zlib/inflate.h | 244 +-
1265 win32port/zlib/inftrees.c | 636 +++---
1266 win32port/zlib/inftrees.h | 124 +-
1267 win32port/zlib/trees.c | 2468 +++++++++++----------
1268 win32port/zlib/trees.h | 256 +--
1269 win32port/zlib/uncompr.c | 118 +-
1270 win32port/zlib/zconf.h | 934 ++++----
1271 win32port/zlib/zlib.h | 3357 ++++++++++++++--------------
1272 win32port/zlib/zutil.c | 642 +++---
1273 win32port/zlib/zutil.h | 526 ++---
1274 69 files changed, 19556 insertions(+), 20145 deletions(-)
1279 - libwebsockets_serve_http_file() now takes a context as first argument
1281 - libwebsockets_get_peer_addresses() now takes a context and wsi as first
1288 - lwsl_...() logging apis, default to stderr but retargetable by user code;
1289 may be used also by user code
1291 - lws_set_log_level() set which logging apis are able to emit (defaults to
1292 notice, warn, err severities), optionally set the emit callback
1294 - lwsl_emit_syslog() helper callback emits to syslog
1296 - lws_daemonize() helper code that forks the app into a headless daemon
1297 properly, maintains a lock file with pid in suitable for sysvinit etc to
1300 - LWS_CALLBACK_HTTP_FILE_COMPLETION callback added since http file
1301 transfer is now asynchronous (see test server code)
1303 - lws_frame_is_binary() from a wsi pointer, let you know if the received
1304 data was sent in BINARY mode
1310 - libwebsockets_fork_service_loop() - no longer supported (had intractable problems)
1311 arrange your code to act from the user callback instead from same
1312 process context as the service loop
1314 - libwebsockets_broadcast() - use libwebsocket_callback_on_writable[_all_protocol]()
1315 instead from same process context as the service loop. See the test apps
1318 - x-google-mux() removed until someone wants it
1320 - pre -v13 (ancient) protocol support removed
1326 - echo test server and client compatible with echo.websocket.org added
1328 - many new configure options (see README.build) to reduce footprint of the
1329 library to what you actually need, eg, --without-client and
1332 - http + websocket server can build to as little as 12K .text for ARM
1334 - no more MAX_CLIENTS limitation; adapts to support the max number of fds
1335 allowed to the process by ulimit, defaults to 1024 on Fedora and
1336 Ubuntu. Use ulimit to control this without needing to configure
1337 the library. Code here is smaller and faster.
1339 - adaptive ratio of listen socket to connection socket service allows
1340 good behaviour under Apache ab test load. Tested with thousands
1341 of simultaneous connections
1343 - reduction in per-connection memory footprint by moving to a union to hold
1344 mutually-exclusive state for the connection
1346 - robustness: Out of Memory taken care of for all allocation code now
1348 - internal getifaddrs option if your toolchain lacks it (some uclibc)
1350 - configurable memory limit for deflate operations
1352 - improvements in SSL code nonblocking operation, possible hang solved,
1353 some SSL operations broken down into pollable states so there is
1354 no library blocking, timeout coverage for SSL_connect
1356 - extpoll test server merged into single test server source
1358 - robustness: library should deal with all recoverable socket conditions
1360 - rx flowcontrol for backpressure notification fixed and implmeneted
1361 correctly in the test server
1363 - optimal lexical parser added for header processing; all headers in a
1364 single 276-byte state table
1366 - latency tracking api added (configure --with-latency)
1368 - Improved in-tree documentation, REAME.build, README.coding,
1369 README.test-apps, changelog
1374 v1.0-chrome25-firefox17 (6cd1ea9b005933f)