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,
152 6) struct lws_client_connect_info has a new member
154 const char *parent_wsi
156 if non-NULL, the client wsi is set to be a child of parent_wsi. This ensures
157 if parent_wsi closes, then the client child is closed just before.
166 1) There is now a "permessage-deflate" / RFC7692 implementation. It's very
167 similar to "deflate-frame" we have offered for a long while; deflate-frame is
168 now provided as an alias of permessage-deflate.
170 The main differences are that the new permessage-deflate implementation:
172 - properly performs streaming respecting input and output buffer limits. The
173 old deflate-frame implementation could only work on complete deflate input
174 and produce complete inflate output for each frame. The new implementation
175 only mallocs buffers at initialization.
177 - goes around the event loop after each input package is processed allowing
178 interleaved output processing. The RX flow control api can be used to
179 force compressed input processing to match the rate of compressed output
180 processing (test--echo shows an example of how to do this).
182 - when being "deflate-frame" for compatibility he uses the same default zlib
183 settings as the old "deflate-frame", but instead of exponentially increasing
184 malloc allocations until the whole output will fit, he observes the default
185 input and output chunking buffer sizes of "permessage-deflate", that's
186 1024 in and 1024 out at a time.
188 2) deflate-stream has been disabled for many versions (for over a year) and is
189 now removed. Browsers are now standardizing on "permessage-deflate" / RFC7692
191 3) struct lws_extension is simplified, and lws extensions now have a public
192 api (their callback) for use in user code to compose extensions and options
193 the user code wants. lws_get_internal_exts() is deprecated but kept around
194 as a NOP. The changes allow one extension implementation to go by different
195 names and allows the user client code to control option offers per-ext.
197 The test client and server are updated to use the new way. If you use
198 the old way it should still work, but extensions will be disabled until you
201 Extensions are now responsible for allocating and per-instance private struct
202 at instance construction time and freeing it when the instance is destroyed.
203 Not needing to know the size means the extension's struct can be opaque
210 1) The info struct gained three new members
212 - max_http_header_data: 0 for default (1024) or set the maximum amount of known
213 http header payload that lws can deal with. Payload in unknown http
214 headers is dropped silently. If for some reason you need to send huge
215 cookies or other HTTP-level headers, you can now increase this at context-
218 - max_http_header_pool: 0 for default (16) or set the maximum amount of http
219 headers that can be tracked by lws in this context. For the server, if
220 the header pool is completely in use then accepts on the listen socket
221 are disabled until one becomes free. For the client, if you simultaneously
222 have pending connects for more than this number of client connections,
223 additional connects will fail until some of the pending connections timeout
226 - timeout_secs: 0 for default (currently 20s), or set the library's
227 network activity timeout to the given number of seconds
229 HTTP header processing in lws only exists until just after the first main
230 callback after the HTTP handshake... for ws connections that is ESTABLISHED and
231 for HTTP connections the HTTP callback.
233 So these settings are not related to the maximum number of simultaneous
234 connections, but the number of HTTP handshakes that may be expected or ongoing,
235 or have just completed, at one time. The reason it's useful is it changes the
236 memory allocation for header processing to be one-time at context creation
237 instead of every time there is a new connection, and gives you control over
240 Setting max_http_header_pool to 1 is fine it will just queue incoming
241 connections before the accept as necessary, you can still have as many
242 simultaneous post-header connections as you like. Since the http header
243 processing is completed and the allocation released after ESTABLISHED or the
244 HTTP callback, even with a pool of 1 many connections can be handled rapidly.
246 2) There is a new callback that allows the user code to get acccess to the
247 optional close code + aux data that may have been sent by the peer.
249 LWS_CALLBACK_WS_PEER_INITIATED_CLOSE:
250 The peer has sent an unsolicited Close WS packet. @in and
251 @len are the optional close code (first 2 bytes, network
252 order) and the optional additional information which is not
253 defined in the standard, and may be a string or non-human-
255 If you return 0 lws will echo the close and then close the
256 connection. If you return nonzero lws will just close the
259 As usual not handling it does the right thing, if you're not interested in it
262 The test server has "open and close" testing buttons at the bottom, if you
263 open and close that connection, on close it will send a close code 3000 decimal
264 and the string "Bye!" as the aux data.
266 The test server dumb-increment callback handles this callback reason and prints
268 lwsts[15714]: LWS_CALLBACK_WS_PEER_INITIATED_CLOSE: len 6
269 lwsts[15714]: 0: 0x0B
270 lwsts[15714]: 1: 0xB8
271 lwsts[15714]: 2: 0x42
272 lwsts[15714]: 3: 0x79
273 lwsts[15714]: 4: 0x65
274 lwsts[15714]: 5: 0x21
276 3) There is a new API to allow the user code to control the content of the
277 close frame sent when about to return nonzero from the user callback to
278 indicate the connection should close.
281 * lws_close_reason - Set reason and aux data to send with Close packet
282 * If you are going to return nonzero from the callback
283 * requesting the connection to close, you can optionally
284 * call this to set the reason the peer will be told if
287 * @wsi: The websocket connection to set the close reason on
288 * @status: A valid close status from websocket standard
289 * @buf: NULL or buffer containing up to 124 bytes of auxiliary data
290 * @len: Length of data in @buf to send
292 LWS_VISIBLE LWS_EXTERN void
293 lws_close_reason(struct lws *wsi, enum lws_close_status status,
294 unsigned char *buf, size_t len);
296 An extra button is added to the "open and close" test server page that requests
297 that the test server close the connection from his end.
299 The test server code will do so by
301 lws_close_reason(wsi, LWS_CLOSE_STATUS_GOINGAWAY,
302 (unsigned char *)"seeya", 5);
305 The browser shows the close code and reason he received
307 websocket connection CLOSED, code: 1001, reason: seeya
309 4) There's a new context creation time option flag
311 LWS_SERVER_OPTION_VALIDATE_UTF8
313 if you set it in info->options, then TEXT and CLOSE frames will get checked to
314 confirm that they contain valid UTF-8. If they don't, the connection will get
317 5) ECDH Certs are now supported. Enable the CMake option
319 cmake .. -DLWS_SSL_SERVER_WITH_ECDH_CERT=1
321 **and** the info->options flag
323 LWS_SERVER_OPTION_SSL_ECDH
325 to build in support and select it at runtime.
327 6) There's a new api lws_parse_uri() that simplifies chopping up
328 https://xxx:yyy/zzz uris into parts nicely. The test client now uses this
329 to allow proper uris as well as the old address style.
331 7) SMP support is integrated into LWS without any internal threading. It's
332 very simple to use, libwebsockets-test-server-pthread shows how to do it,
333 use -j <n> argument there to control the number of service threads up to 32.
335 Two new members are added to the info struct
337 unsigned int count_threads;
338 unsigned int fd_limit_per_thread;
340 leave them at the default 0 to get the normal singlethreaded service loop.
342 Set count_threads to n to tell lws you will have n simultaneous service threads
343 operating on the context.
345 There is still a single listen socket on one port, no matter how many
348 When a connection is made, it is accepted by the service thread with the least
349 connections active to perform load balancing.
351 The user code is responsible for spawning n threads running the service loop
352 associated to a specific tsi (Thread Service Index, 0 .. n - 1). See
353 the libwebsockets-test-server-pthread for how to do.
355 If you leave fd_limit_per_thread at 0, then the process limit of fds is shared
356 between the service threads; if you process was allowed 1024 fds overall then
357 each thread is limited to 1024 / n.
359 You can set fd_limit_per_thread to a nonzero number to control this manually, eg
360 the overall supported fd limit is less than the process allowance.
362 You can control the context basic data allocation for multithreading from Cmake
363 using -DLWS_MAX_SMP=, if not given it's set to 32. The serv_buf allocation
364 for the threads (currently 4096) is made at runtime only for active threads.
366 Because lws will limit the requested number of actual threads supported
367 according to LWS_MAX_SMP, there is an api lws_get_count_threads(context) to
368 discover how many threads were actually allowed when the context was created.
370 It's required to implement locking in the user code in the same way that
371 libwebsockets-test-server-pthread does it, for the FD locking callbacks.
373 If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the
374 library. If more than 1, a small amount of pthread mutex code is built into
379 LWS_VISIBLE struct lws *
380 lws_adopt_socket(struct lws_context *context, lws_sockfd_type accept_fd)
382 allows foreign sockets accepted by non-lws code to be adopted by lws as if they
383 had just been accepted by lws' own listen socket.
385 9) X-Real-IP: header has been added as WSI_TOKEN_HTTP_X_REAL_IP
387 10) Libuv support is added, there are new related user apis
389 typedef void (lws_uv_signal_cb_t)(uv_loop_t *l, uv_signal_t *w, int revents);
391 LWS_VISIBLE LWS_EXTERN int
392 lws_uv_sigint_cfg(struct lws_context *context, int use_uv_sigint,
393 lws_uv_signal_cb_t *cb);
395 LWS_VISIBLE LWS_EXTERN int
396 lws_uv_initloop(struct lws_context *context, uv_loop_t *loop, int tsi);
399 lws_uv_sigint_cb(uv_loop_t *loop, uv_signal_t *watcher, int revents);
409 1) LWS_SEND_BUFFER_POST_PADDING is now 0 and deprecated. You can remove it; if
410 you still use it, obviously it does nothing. Old binary code with nonzero
411 LWS_SEND_BUFFER_POST_PADDING is perfectly compatible, the old code just
412 allocated a buffer bigger than the library is going to use.
414 The example apps no longer use LWS_SEND_BUFFER_POST_PADDING.
416 The only path who made use of it was sending with LWS_WRITE_CLOSE --->
418 2) Because of lws_close_reason() formalizing handling close frames,
419 LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send
420 close frames...close frame content should be managed using lws_close_reason()
423 3) We check for invalid CLOSE codes and complain about protocol violation in
424 our close code. But it changes little since we were in the middle of closing
427 4) zero-length RX frames and zero length TX frames are now allowed.
429 5) Pings and close used to be limited to 124 bytes, the correct limit is 125
430 so that is now also allowed.
432 6) LWS_PRE is provided as a synonym for LWS_SEND_BUFFER_PRE_PADDING, either is
435 7) There's generic support for RFC7462 style extension options built into the
436 library now. As a consequence, a field "options" is added to lws_extension.
437 It can be NULL if there are no options on the extension. Extension internal
438 info is part of the public abi because extensions may be implemented outside
441 8) WSI_TOKEN_PROXY enum was accidentally defined to collide with another token
442 of value 73. That's now corrected and WSI_TOKEN_PROXY moved to his own place at
445 9) With the addition of libuv support, libev is not the only event loop
446 library in town and his api names must be elaborated with _ev_
448 Callback typedef: lws_signal_cb ---> lws_ev_signal_cb_t
449 lws_sigint_cfg --> lws_ev_sigint_cfg
450 lws_initloop --> lws_ev_initloop
451 lws_sigint_cb --> lws_ev_sigint_cb
453 10) Libev support is made compatible with multithreaded service,
454 lws_ev_initloop (was lws_initloop) gets an extra argument for the
455 thread service index (use 0 if you will just have 1 service thread).
457 LWS_VISIBLE LWS_EXTERN int
458 lws_ev_initloop(struct lws_context *context, ev_loop_t *loop, int tsi);
461 v1.6.0-chrome48-firefox42
462 =======================
464 Major API improvements
465 ----------------------
467 v1.6.0 has many cleanups and improvements in the API. Although at first it
468 looks pretty drastic, user code will only need four actions to update it.
470 - Do the three search/replaces in your user code, /libwebsocket_/lws_/,
471 /libwebsockets_/lws_/, and /struct\ libwebsocket/struct\ lws/
473 - Remove the context parameter from your user callbacks
475 - Remove context as the first parameter from the "Eleven APIS" listed in the
476 User Api Changes section
478 - Add lws_get_context(wsi) as the first parameter on the "Three APIS" listed
479 in the User Api Changes section, and anywhere else you still need context
481 That's it... generally only a handful of the 14 affected APIs are actually in
482 use in your user code and you can find them quickest by compiling and visiting
483 the errors each in turn. And the end results are much cleaner, more
484 predictable and maintainable.
490 1) lws now exposes his internal platform file abstraction in a way that can be
491 both used by user code to make it platform-agnostic, and be overridden or
492 subclassed by user code. This allows things like handling the URI "directory
493 space" as a virtual filesystem that may or may not be backed by a regular
494 filesystem. One example use is serving files from inside large compressed
495 archive storage without having to unpack anything except the file being
498 The test server shows how to use it, basically the platform-specific part of
499 lws prepares a file operations structure that lives in the lws context.
501 Helpers are provided to also leverage these platform-independent file handling
504 static inline lws_filefd_type
505 lws_plat_file_open(struct lws *wsi, const char *filename,
506 unsigned long *filelen, int flags)
508 lws_plat_file_close(struct lws *wsi, lws_filefd_type fd)
510 static inline unsigned long
511 lws_plat_file_seek_cur(struct lws *wsi, lws_filefd_type fd, long offset)
514 lws_plat_file_read(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
515 unsigned char *buf, unsigned long len)
518 lws_plat_file_write(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
519 unsigned char *buf, unsigned long len)
521 The user code can also override or subclass the file operations, to either
522 wrap or replace them. An example is shown in test server.
524 A wsi can be associated with the file activity, allowing per-connection
525 authentication and state to be used when interpreting the file request.
527 2) A new API void * lws_wsi_user(struct lws *wsi) lets you get the pointer to
528 the user data associated with the wsi, just from the wsi.
530 3) URI argument handling. Libwebsockets parses and protects URI arguments
531 like test.html?arg1=1&arg2=2, it decodes %xx uriencoding format and reduces
532 path attacks like ../.../../etc/passwd so they cannot go behind the web
533 server's /. There is a list of confirmed attacks we're proof against in
534 ./test-server/attack.sh.
536 There is a new API lws_hdr_copy_fragment that should be used now to access
537 the URI arguments (it returns the fragments length)
539 while (lws_hdr_copy_fragment(wsi, buf, sizeof(buf),
540 WSI_TOKEN_HTTP_URI_ARGS, n) > 0) {
541 lwsl_info("URI Arg %d: %s\n", ++n, buf);
544 For the example above, calling with n=0 will return "arg1=1" and n=1 "arg2=2".
545 All legal uriencodings will have been reduced in those strings.
547 lws_hdr_copy_fragment() returns the length of the x=y fragment, so it's also
548 possible to deal with arguments containing %00. If you don't care about that,
549 the returned string has '\0' appended to simplify processing.
557 - lws_callback_on_writable_all_protocol(const struct lws_protocols *protocol)
558 - lws_callback_all_protocol(const struct lws_protocols *protocol)
559 - lws_rx_flow_allow_all_protocol(lws_rx_flow_allow_all_protocol)
561 Now take an additional pointer to the lws_context in their first argument.
563 The reason for this change is struct lws_protocols has been changed to remove
564 members that lws used for private storage: so the protocols struct in now
565 truly const and may be reused serially or simultaneously by different contexts.
569 LWS_VISIBLE LWS_EXTERN int
570 lws_add_http_header_by_name(struct lws_context *context,
572 const unsigned char *name,
573 const unsigned char *value,
577 LWS_VISIBLE LWS_EXTERN int
578 lws_finalize_http_header(struct lws_context *context,
582 LWS_VISIBLE LWS_EXTERN int
583 lws_add_http_header_by_token(struct lws_context *context,
585 enum lws_token_indexes token,
586 const unsigned char *value,
590 LWS_VISIBLE LWS_EXTERN int
591 lws_add_http_header_content_length(struct lws_context *context,
593 unsigned long content_length,
596 LWS_VISIBLE LWS_EXTERN int
597 lws_add_http_header_status(struct lws_context *context, struct lws *wsi,
598 unsigned int code, unsigned char **p,
601 LWS_VISIBLE LWS_EXTERN int
602 lws_serve_http_file(struct lws_context *context, struct lws *wsi,
603 const char *file, const char *content_type,
604 const char *other_headers, int other_headers_len);
605 LWS_VISIBLE LWS_EXTERN int
606 lws_serve_http_file_fragment(struct lws_context *context, struct lws *wsi);
608 LWS_VISIBLE LWS_EXTERN int
609 lws_return_http_status(struct lws_context *context, struct lws *wsi,
610 unsigned int code, const char *html_body);
612 LWS_VISIBLE LWS_EXTERN int
613 lws_callback_on_writable(const struct lws_context *context, struct lws *wsi);
615 LWS_VISIBLE LWS_EXTERN void
616 lws_get_peer_addresses(struct lws_context *context, struct lws *wsi,
617 lws_sockfd_type fd, char *name, int name_len,
618 char *rip, int rip_len);
620 LWS_VISIBLE LWS_EXTERN int
621 lws_read(struct lws_context *context, struct lws *wsi,
622 unsigned char *buf, size_t len);
624 no longer require their initial struct lws_context * parameter.
626 3) Several older apis start with libwebsocket_ or libwebsockets_ while newer ones
627 all begin lws_. These apis have been changed to all begin with lws_.
629 To convert, search-replace
631 - libwebsockets_/lws_
633 - struct\ libwebsocket/struct\ lws
635 4) context parameter removed from user callback.
637 Since almost all apis no longer need the context as a parameter, it's no longer
638 provided at the user callback directly.
640 However if you need it, for ALL callbacks wsi is valid and has a valid context
641 pointer you can recover using lws_get_context(wsi).
644 v1.5-chrome47-firefox41
645 =======================
650 LWS_CALLBACK_CLIENT_CONNECTION_ERROR may provide an error string if in is
651 non-NULL. If so, the string has length len.
653 LWS_SERVER_OPTION_PEER_CERT_NOT_REQUIRED is available to relax the requirement
654 for peer certs if you are using the option to require client certs.
656 LWS_WITHOUT_BUILTIN_SHA1 cmake option forces lws to use SHA1() defined
657 externally, eg, byOpenSSL, and disables build of libwebsockets_SHA1()
660 v1.4-chrome43-firefox36
661 =======================
666 There's a new member in the info struct used to control context creation,
667 ssl_private_key_password, which allows passing into lws the passphrase on
670 There's a new member in struct protocols, id, which is ignored by lws but can
671 be used by the user code to mark the selected protocol by user-defined version
672 or capabliity flag information, for the case multiple versions of a protocol are
675 int lws_is_ssl(wsi) added to allow user code to know if the connection was made
676 over ssl or not. If LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT is used, both
677 ssl and non-ssl connections are possible and may need to be treated differently
680 int lws_partial_buffered(wsi) added... should be checked after any
681 libwebsocket_write that will be followed by another libwebsocket_write inside
682 the same writeable callback. If set, you can't do any more writes until the
683 writeable callback is called again. If you only do one write per writeable callback,
686 HTTP2-related: HTTP2 changes how headers are handled, lws now has new version-
687 agnositic header creation APIs. These do the right thing depending on each
688 connection's HTTP version without the user code having to know or care, except
689 to make sure to use the new APIs for headers (test-server is updated to use
690 them already, so look there for examples)
692 The APIs "render" the headers into a user-provided buffer and bump *p as it
693 is used. If *p reaches end, then the APIs return nonzero for error.
695 LWS_VISIBLE LWS_EXTERN int
696 lws_add_http_header_status(struct libwebsocket_context *context,
697 struct libwebsocket *wsi,
702 Start a response header reporting status like 200, 500, etc
704 LWS_VISIBLE LWS_EXTERN int
705 lws_add_http_header_by_name(struct libwebsocket_context *context,
706 struct libwebsocket *wsi,
707 const unsigned char *name,
708 const unsigned char *value,
713 Add a header like name: value in HTTP1.x
715 LWS_VISIBLE LWS_EXTERN int
716 lws_finalize_http_header(struct libwebsocket_context *context,
717 struct libwebsocket *wsi,
721 Finish off the headers, like add the extra \r\n in HTTP1.x
723 LWS_VISIBLE LWS_EXTERN int
724 lws_add_http_header_by_token(struct libwebsocket_context *context,
725 struct libwebsocket *wsi,
726 enum lws_token_indexes token,
727 const unsigned char *value,
732 Add a header by using a lws token as the name part. In HTTP2, this can be
733 compressed to one or two bytes.
739 protocols struct member no_buffer_all_partial_tx is removed. Under some
740 conditions like rewriting extension such as compression in use, the built-in
741 partial send buffering is the only way to deal with the problem, so turning
742 it off is deprecated.
748 HTTP2-related: API libwebsockets_serve_http_file() takes an extra parameter at
751 int other_headers_len)
753 If you are providing other headers, they must be generated using the new
754 HTTP-version-agnostic APIs, and you must provide the length of them using this
755 additional parameter.
757 struct lws_context_creation_info now has an additional member
758 SSL_CTX *provided_client_ssl_ctx you may set to an externally-initialized
759 SSL_CTX managed outside lws. Defaulting to zero keeps the existing behaviour of
760 lws managing the context, if you memset the struct to 0 or have as a filescope
761 initialized struct in bss, no need to change anything.
764 v1.3-chrome37-firefox30
765 =======================
768 CMakeLists.txt | 447 +++--
772 cmake/LibwebsocketsConfig.cmake.in | 17 +
773 cmake/LibwebsocketsConfigVersion.cmake.in | 11 +
774 config.h.cmake | 18 +
775 cross-ming.cmake | 31 +
776 cross-openwrt-makefile | 91 +
777 lib/client-handshake.c | 205 ++-
778 lib/client-parser.c | 58 +-
779 lib/client.c | 158 +-
780 lib/context.c | 341 ++++
781 lib/extension-deflate-frame.c | 2 +-
782 lib/extension.c | 178 ++
783 lib/handshake.c | 287 +---
784 lib/lextable.h | 338 ++++
786 lib/libwebsockets.c | 2089 +++--------------------
787 lib/libwebsockets.h | 253 ++-
788 lib/lws-plat-unix.c | 404 +++++
789 lib/lws-plat-win.c | 358 ++++
790 lib/minilex.c | 530 +++---
791 lib/output.c | 445 ++---
792 lib/parsers.c | 682 ++++----
793 lib/pollfd.c | 239 +++
794 lib/private-libwebsockets.h | 501 +++++-
795 lib/server-handshake.c | 274 +--
796 lib/server.c | 858 ++++++++--
797 lib/service.c | 517 ++++++
799 lib/ssl-http2.c | 78 +
800 lib/ssl.c | 571 +++++++
801 test-server/attack.sh | 101 +-
802 test-server/test-client.c | 9 +-
803 test-server/test-echo.c | 17 +-
804 test-server/test-fraggle.c | 7 -
805 test-server/test-ping.c | 12 +-
806 test-server/test-server.c | 330 ++--
807 test-server/test.html | 4 +-
808 win32port/client/client.vcxproj | 259 ---
809 win32port/client/client.vcxproj.filters | 39 -
810 .../libwebsocketswin32.vcxproj.filters | 93 -
811 win32port/server/server.vcxproj | 276 ---
812 win32port/server/server.vcxproj.filters | 51 -
813 win32port/win32helpers/gettimeofday.h | 59 +-
814 win32port/win32helpers/netdb.h | 1 -
815 win32port/win32helpers/strings.h | 0
816 win32port/win32helpers/sys/time.h | 1 -
817 win32port/win32helpers/unistd.h | 0
818 win32port/win32helpers/websock-w32.c | 104 --
819 win32port/win32helpers/websock-w32.h | 62 -
820 win32port/win32port.sln | 100 --
821 win32port/zlib/gzio.c | 3 +-
822 55 files changed, 6779 insertions(+), 5059 deletions(-)
828 POST method is supported
830 The protocol 0 / HTTP callback can now get two new kinds of callback,
831 LWS_CALLBACK_HTTP_BODY (in and len are a chunk of the body of the HTTP request)
832 and LWS_CALLBACK_HTTP_BODY_COMPLETION (the expected amount of body has arrived
833 and been passed to the user code already). These callbacks are used with the
834 post method (see the test server for details).
836 The period between the HTTP header completion and the completion of the body
837 processing is protected by a 5s timeout.
839 The chunks are stored in a malloc'd buffer of size protocols[0].rx_buffer_size.
842 New server option you can enable from user code
843 LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT allows non-SSL connections to
844 also be accepted on an SSL listening port. It's disabled unless you enable
848 Two new callbacks are added in protocols[0] that are optional for allowing
849 limited thread access to libwebsockets, LWS_CALLBACK_LOCK_POLL and
850 LWS_CALLBACK_UNLOCK_POLL.
852 If you use them, they protect internal and external poll list changes, but if
853 you want to use external thread access to libwebsocket_callback_on_writable()
854 you have to implement your locking here even if you don't use external
857 If you will use another thread for this, take a lot of care about managing
858 your list of live wsi by doing it from ESTABLISHED and CLOSED callbacks
859 (with your own locking).
861 If you configure cmake with -DLWS_WITH_LIBEV=1 then the code allowing the libev
862 eventloop instead of the default poll() one will also be compiled in. But to
863 use it, you must also set the LWS_SERVER_OPTION_LIBEV flag on the context
864 creation info struct options member.
866 IPV6 is supported and enabled by default except for Windows, you can disable
867 the support at build-time by giving -DLWS_IPV6=, and disable use of it even if
868 compiled in by making sure the flag LWS_SERVER_OPTION_DISABLE_IPV6 is set on
869 the context creation info struct options member.
871 You can give LWS_SERVER_OPTION_DISABLE_OS_CA_CERTS option flag to
872 guarantee the OS CAs will not be used, even if that support was selected at
875 Optional "token limits" may be enforced by setting the member "token_limits"
876 in struct lws_context_creation_info to point to a struct lws_token_limits.
877 NULL means no token limits used for compatibility.
883 Extra optional argument to libwebsockets_serve_http_file() allows injecion
884 of HTTP headers into the canned response. Eg, cookies may be added like
885 that without getting involved in having to send the header by hand.
887 A new info member http_proxy_address may be used at context creation time to
888 set the http proxy. If non-NULL, it overrides http_proxy environment var.
890 Cmake supports LWS_SSL_CLIENT_USE_OS_CA_CERTS defaulting to on, which gets
891 the client to use the OS CA Roots. If you're worried somebody with the
892 ability to forge for force creation of a client cert from the root CA in
893 your OS, you should disable this since your selfsigned $0 cert is a lot safer
897 v1.23-chrome32-firefox24
898 ========================
901 CMakeLists.txt | 573 ++++++++----
902 COPYING | 503 -----------
903 INSTALL | 365 --------
905 README.build | 371 ++------
906 README.coding | 63 ++
907 autogen.sh | 1578 ---------------------------------
909 cmake/FindGit.cmake | 163 ++++
910 cmake/FindOpenSSLbins.cmake | 15 +-
911 cmake/UseRPMTools.cmake | 176 ++++
912 config.h.cmake | 25 +-
913 configure.ac | 226 -----
914 cross-arm-linux-gnueabihf.cmake | 28 +
915 lib/Makefile.am | 89 --
916 lib/base64-decode.c | 98 +-
917 lib/client-handshake.c | 123 ++-
918 lib/client-parser.c | 19 +-
919 lib/client.c | 145 ++-
920 lib/daemonize.c | 4 +-
921 lib/extension.c | 2 +-
922 lib/getifaddrs.h | 4 +-
923 lib/handshake.c | 76 +-
924 lib/libwebsockets.c | 491 ++++++----
925 lib/libwebsockets.h | 164 ++--
926 lib/output.c | 214 ++++-
927 lib/parsers.c | 102 +--
928 lib/private-libwebsockets.h | 66 +-
929 lib/server-handshake.c | 5 +-
932 libwebsockets-api-doc.html | 249 +++---
933 libwebsockets.pc.in | 11 -
934 libwebsockets.spec | 14 +-
936 scripts/FindLibWebSockets.cmake | 33 +
937 scripts/kernel-doc | 1 +
938 test-server/Makefile.am | 131 ---
939 test-server/leaf.jpg | Bin 0 -> 2477518 bytes
940 test-server/test-client.c | 78 +-
941 test-server/test-echo.c | 33 +-
942 test-server/test-fraggle.c | 26 +-
943 test-server/test-ping.c | 15 +-
944 test-server/test-server.c | 197 +++-
945 test-server/test.html | 5 +-
946 win32port/win32helpers/gettimeofday.c | 74 +-
947 win32port/win32helpers/websock-w32.h | 6 +-
948 48 files changed, 2493 insertions(+), 4212 deletions(-)
954 - You can now call libwebsocket_callback_on_writable() on http connectons,
955 and get a LWS_CALLBACK_HTTP_WRITEABLE callback, the same way you can
956 regulate writes with a websocket protocol connection.
958 - A new member in the context creation parameter struct "ssl_cipher_list" is
959 added, replacing CIPHERS_LIST_STRING. NULL means use the ssl library
960 default list of ciphers.
962 - Not really an api addition, but libwebsocket_service_fd() will now zero
963 the revents field of the pollfd it was called with if it handled the
964 descriptor. So you can tell if it is a non-lws fd by checking revents
965 after the service call... if it's still nonzero, the descriptor
966 belongs to you and you need to take care of it.
968 - libwebsocket_rx_flow_allow_all_protocol(protocol) will unthrottle all
969 connections with the established protocol. It's designed to be
970 called from user server code when it sees it can accept more input
971 and may have throttled connections using the server rx flow apis
972 while it was unable to accept any other input The user server code
973 then does not have to try to track while connections it choked, this
974 will free up all of them in one call.
976 - there's a new, optional callback LWS_CALLBACK_CLOSED_HTTP which gets
977 called when an HTTP protocol socket closes
979 - for LWS_CALLBACK_FILTER_PROTOCOL_CONNECTION callback, the user_space alloc
980 has already been done before the callback happens. That means we can
981 use the user parameter to the callback to contain the user pointer, and
982 move the protocol name to the "in" parameter. The docs for this
983 callback are also updated to reflect how to check headers in there.
985 - libwebsocket_client_connect() is now properly nonblocking and async. See
986 README.coding and test-client.c for information on the callbacks you
987 can rely on controlling the async connection period with.
989 - if your OS does not support the http_proxy environment variable convention
990 (eg, reportedly OSX), you can use a new api libwebsocket_set_proxy()
991 to set the proxy details in between context creation and the connection
992 action. For OSes that support http_proxy, that's used automatically.
997 - the external poll callbacks now get the socket descriptor coming from the
998 "in" parameter. The user parameter provides the user_space for the
999 wsi as it normally does on the other callbacks.
1000 LWS_CALLBACK_FILTER_NETWORK_CONNECTION also has the socket descriptor
1001 delivered by @in now instead of @user.
1003 - libwebsocket_write() now returns -1 for error, or the amount of data
1004 actually accepted for send. Under load, the OS may signal it is
1005 ready to send new data on the socket, but have only a restricted
1006 amount of memory to buffer the packet compared to usual.
1012 - libwebsocket_ensure_user_space() is removed from the public api, if you
1013 were using it to get user_space, you need to adapt your code to only
1014 use user_space inside the user callback.
1016 - CIPHERS_LIST_STRING is removed
1018 - autotools build has been removed. See README.build for info on how to
1019 use CMake for your platform
1022 v1.21-chrome26-firefox18
1023 ========================
1025 - Fixes buffer overflow bug in max frame size handling if you used the
1026 default protocol buffer size. If you declared rx_buffer_size in your
1027 protocol, which is recommended anyway, your code was unaffected.
1029 v1.2-chrome26-firefox18
1030 =======================
1036 CMakeLists.txt | 544 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1037 LICENSE | 526 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1040 README.build | 258 ++++++++++++++++++++++++++++++++-----
1041 README.coding | 52 ++++++++
1042 changelog | 136 ++++++++++++++++++++
1043 cmake/FindOpenSSLbins.cmake | 33 +++++
1044 config.h.cmake | 173 +++++++++++++++++++++++++
1045 configure.ac | 22 +++-
1046 lib/Makefile.am | 20 ++-
1047 lib/base64-decode.c | 2 +-
1048 lib/client-handshake.c | 190 +++++++++++-----------------
1049 lib/client-parser.c | 88 +++++++------
1050 lib/client.c | 384 ++++++++++++++++++++++++++++++-------------------------
1051 lib/daemonize.c | 32 +++--
1052 lib/extension-deflate-frame.c | 58 +++++----
1053 lib/extension-deflate-stream.c | 19 ++-
1054 lib/extension-deflate-stream.h | 4 +-
1055 lib/extension.c | 11 +-
1056 lib/getifaddrs.c | 315 +++++++++++++++++++++++-----------------------
1057 lib/getifaddrs.h | 30 ++---
1058 lib/handshake.c | 124 +++++++++++-------
1059 lib/libwebsockets.c | 736 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------
1060 lib/libwebsockets.h | 237 ++++++++++++++++++++++------------
1061 lib/output.c | 192 +++++++++++-----------------
1062 lib/parsers.c | 966 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------
1063 lib/private-libwebsockets.h | 225 +++++++++++++++++++++------------
1064 lib/server-handshake.c | 82 ++++++------
1065 lib/server.c | 96 +++++++-------
1066 libwebsockets-api-doc.html | 189 ++++++++++++++++++----------
1067 libwebsockets.spec | 17 +--
1068 test-server/attack.sh | 148 ++++++++++++++++++++++
1069 test-server/test-client.c | 125 +++++++++---------
1070 test-server/test-echo.c | 31 +++--
1071 test-server/test-fraggle.c | 32 ++---
1072 test-server/test-ping.c | 52 ++++----
1073 test-server/test-server.c | 129 ++++++++++++-------
1074 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj | 279 ----------------------------------------
1075 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj.filters | 23 +++-
1076 41 files changed, 4398 insertions(+), 2219 deletions(-)
1082 - lws_get_library_version() returns a const char * with a string like
1083 "1.1 9e7f737", representing the library version from configure.ac
1084 and the git HEAD hash the library was built from
1086 - TCP Keepalive can now optionally be applied to all lws sockets, on Linux
1087 also with controllable timeout, number of probes and probe interval.
1088 (On BSD type OS, you can only use system default settings for the
1089 timing and retries, although enabling it is supported by setting
1090 ka_time to nonzero, the exact value has no meaning.)
1091 This enables detection of idle connections which are logically okay,
1092 but are in fact dead, due to network connectivity issues at the server,
1093 client, or any intermediary. By default it's not enabled, but you
1094 can enable it by setting a non-zero timeout (in seconds) at the new
1095 ka_time member at context creation time.
1097 - Two new optional user callbacks added, LWS_CALLBACK_PROTOCOL_DESTROY which
1098 is called one-time per protocol as the context is being destroyed, and
1099 LWS_CALLBACK_PROTOCOL_INIT which is called when the context is created
1100 and the protocols are added, again it's a one-time affair.
1101 This lets you manage per-protocol allocations properly including
1102 cleaning up after yourself when the server goes down.
1107 - libwebsocket_create_context() has changed from taking a ton of parameters
1108 to just taking a pointer to a struct containing the parameters. The
1109 struct lws_context_creation_info is in libwebsockets.h, the members
1110 are in the same order as when they were parameters to the call
1111 previously. The test apps are all updated accordingly so you can
1112 see example code there.
1114 - Header tokens are now deleted after the websocket connection is
1115 established. Not just the header data is saved, but the pointer and
1116 length array is also removed from (union) scope saving several hundred
1117 bytes per connection once it is established
1119 - struct libwebsocket_protocols has a new member rx_buffer_size, this
1120 controls rx buffer size per connection of that protocol now. Sources
1121 for apps built against older versions of the library won't declare
1122 this in their protocols, defaulting it to 0. Zero buffer is legal,
1123 it causes a default buffer to be allocated (currently 4096)
1125 If you want to receive only atomic frames in your user callback, you
1126 should set this to greater than your largest frame size. If a frame
1127 comes that exceeds that, no error occurs but the callback happens as
1128 soon as the buffer limit is reached, and again if it is reached again
1129 or the frame completes. You can detect that has happened by seeing
1130 there is still frame content pending using
1131 libwebsockets_remaining_packet_payload()
1133 By correctly setting this, you can save a lot of memory when your
1134 protocol has small frames (see the test server and client sources).
1136 - LWS_MAX_HEADER_LEN now defaults to 1024 and is the total amount of known
1137 header payload lws can cope with, that includes the GET URL, origin
1138 etc. Headers not understood by lws are ignored and their payload
1139 not included in this.
1145 - The configuration-time option MAX_USER_RX_BUFFER has been replaced by a
1146 buffer size chosen per-protocol. For compatibility, there's a default
1147 of 4096 rx buffer, but user code should set the appropriate size for
1148 the protocol frames.
1150 - LWS_INITIAL_HDR_ALLOC and LWS_ADDITIONAL_HDR_ALLOC are no longer needed
1151 and have been removed. There's a new header management scheme that
1152 handles them in a much more compact way.
1154 - libwebsockets_hangup_on_client() is removed. If you want to close the
1155 connection you must do so from the user callback and by returning
1158 - libwebsocket_close_and_free_session() is now private to the library code
1159 only and not exposed for user code. If you want to close the
1160 connection, you must do so from the user callback by returning -1
1167 - Cmake project file added, aimed initially at Windows support: this replaces
1168 the visual studio project files that were in the tree until now.
1170 - CyaSSL now supported in place of OpenSSL (--use-cyassl on configure)
1172 - PATH_MAX or MAX_PATH no longer needed
1174 - cutomizable frame rx buffer size by protocol
1176 - optional TCP keepalive so dead peers can be detected, can be enabled at
1177 context-creation time
1179 - valgrind-clean: no SSL or CyaSSL: completely clean. With OpenSSL, 88 bytes
1180 lost at OpenSSL library init and symptomless reports of uninitialized
1181 memory usage... seems to be a known and ignored problem at OpenSSL
1183 - By default debug is enabled and the library is built for -O0 -g to faclitate
1184 that. Use --disable-debug configure option to build instead with -O4
1185 and no -g (debug info), obviously providing best performance and
1186 reduced binary size.
1188 - 1.0 introduced some code to try to not deflate small frames, however this
1189 seems to break when confronted with a mixture of frames above and
1190 below the threshold, so it's removed. Veto the compression extension
1191 in your user callback if you will typically have very small frames.
1193 - There are many memory usage improvements, both a reduction in malloc/
1194 realloc and architectural changes. A websocket connection now
1195 consumes only 296 bytes with SSL or 272 bytes without on x86_64,
1196 during header processing an additional 1262 bytes is allocated in a
1197 single malloc, but is freed when the websocket connection starts.
1198 The RX frame buffer defined by the protocol in user
1199 code is also allocated per connection, this represents the largest
1200 frame you can receive atomically in that protocol.
1202 - On ARM9 build, just http+ws server no extensions or ssl, <12Kbytes .text
1203 and 112 bytes per connection (+1328 only during header processing)
1206 v1.1-chrome26-firefox18
1207 =======================
1213 README-test-server | 291 ---
1214 README.build | 239 ++
1215 README.coding | 138 ++
1217 README.test-apps | 272 +++
1218 configure.ac | 116 +-
1219 lib/Makefile.am | 55 +-
1220 lib/base64-decode.c | 5 +-
1221 lib/client-handshake.c | 121 +-
1222 lib/client-parser.c | 394 ++++
1223 lib/client.c | 807 +++++++
1224 lib/daemonize.c | 212 ++
1225 lib/extension-deflate-frame.c | 132 +-
1226 lib/extension-deflate-stream.c | 12 +-
1227 lib/extension-x-google-mux.c | 1223 ----------
1228 lib/extension-x-google-mux.h | 96 -
1229 lib/extension.c | 8 -
1230 lib/getifaddrs.c | 271 +++
1231 lib/getifaddrs.h | 76 +
1232 lib/handshake.c | 582 +----
1233 lib/libwebsockets.c | 2493 ++++++---------------
1234 lib/libwebsockets.h | 115 +-
1236 lib/minilex.c | 440 ++++
1237 lib/output.c | 628 ++++++
1238 lib/parsers.c | 2016 +++++------------
1239 lib/private-libwebsockets.h | 284 +--
1240 lib/server-handshake.c | 275 +++
1241 lib/server.c | 377 ++++
1242 libwebsockets-api-doc.html | 300 +--
1244 test-server/Makefile.am | 111 +-
1245 test-server/libwebsockets.org-logo.png | Bin 0 -> 7029 bytes
1246 test-server/test-client.c | 45 +-
1247 test-server/test-echo.c | 330 +++
1248 test-server/test-fraggle.c | 20 +-
1249 test-server/test-ping.c | 22 +-
1250 test-server/test-server-extpoll.c | 554 -----
1251 test-server/test-server.c | 349 ++-
1252 test-server/test.html | 3 +-
1253 win32port/zlib/ZLib.vcxproj | 749 ++++---
1254 win32port/zlib/ZLib.vcxproj.filters | 188 +-
1255 win32port/zlib/adler32.c | 348 ++-
1256 win32port/zlib/compress.c | 160 +-
1257 win32port/zlib/crc32.c | 867 ++++----
1258 win32port/zlib/crc32.h | 882 ++++----
1259 win32port/zlib/deflate.c | 3799 +++++++++++++++-----------------
1260 win32port/zlib/deflate.h | 688 +++---
1261 win32port/zlib/gzclose.c | 50 +-
1262 win32port/zlib/gzguts.h | 325 ++-
1263 win32port/zlib/gzlib.c | 1157 +++++-----
1264 win32port/zlib/gzread.c | 1242 ++++++-----
1265 win32port/zlib/gzwrite.c | 1096 +++++----
1266 win32port/zlib/infback.c | 1272 ++++++-----
1267 win32port/zlib/inffast.c | 680 +++---
1268 win32port/zlib/inffast.h | 22 +-
1269 win32port/zlib/inffixed.h | 188 +-
1270 win32port/zlib/inflate.c | 2976 +++++++++++++------------
1271 win32port/zlib/inflate.h | 244 +-
1272 win32port/zlib/inftrees.c | 636 +++---
1273 win32port/zlib/inftrees.h | 124 +-
1274 win32port/zlib/trees.c | 2468 +++++++++++----------
1275 win32port/zlib/trees.h | 256 +--
1276 win32port/zlib/uncompr.c | 118 +-
1277 win32port/zlib/zconf.h | 934 ++++----
1278 win32port/zlib/zlib.h | 3357 ++++++++++++++--------------
1279 win32port/zlib/zutil.c | 642 +++---
1280 win32port/zlib/zutil.h | 526 ++---
1281 69 files changed, 19556 insertions(+), 20145 deletions(-)
1286 - libwebsockets_serve_http_file() now takes a context as first argument
1288 - libwebsockets_get_peer_addresses() now takes a context and wsi as first
1295 - lwsl_...() logging apis, default to stderr but retargetable by user code;
1296 may be used also by user code
1298 - lws_set_log_level() set which logging apis are able to emit (defaults to
1299 notice, warn, err severities), optionally set the emit callback
1301 - lwsl_emit_syslog() helper callback emits to syslog
1303 - lws_daemonize() helper code that forks the app into a headless daemon
1304 properly, maintains a lock file with pid in suitable for sysvinit etc to
1307 - LWS_CALLBACK_HTTP_FILE_COMPLETION callback added since http file
1308 transfer is now asynchronous (see test server code)
1310 - lws_frame_is_binary() from a wsi pointer, let you know if the received
1311 data was sent in BINARY mode
1317 - libwebsockets_fork_service_loop() - no longer supported (had intractable problems)
1318 arrange your code to act from the user callback instead from same
1319 process context as the service loop
1321 - libwebsockets_broadcast() - use libwebsocket_callback_on_writable[_all_protocol]()
1322 instead from same process context as the service loop. See the test apps
1325 - x-google-mux() removed until someone wants it
1327 - pre -v13 (ancient) protocol support removed
1333 - echo test server and client compatible with echo.websocket.org added
1335 - many new configure options (see README.build) to reduce footprint of the
1336 library to what you actually need, eg, --without-client and
1339 - http + websocket server can build to as little as 12K .text for ARM
1341 - no more MAX_CLIENTS limitation; adapts to support the max number of fds
1342 allowed to the process by ulimit, defaults to 1024 on Fedora and
1343 Ubuntu. Use ulimit to control this without needing to configure
1344 the library. Code here is smaller and faster.
1346 - adaptive ratio of listen socket to connection socket service allows
1347 good behaviour under Apache ab test load. Tested with thousands
1348 of simultaneous connections
1350 - reduction in per-connection memory footprint by moving to a union to hold
1351 mutually-exclusive state for the connection
1353 - robustness: Out of Memory taken care of for all allocation code now
1355 - internal getifaddrs option if your toolchain lacks it (some uclibc)
1357 - configurable memory limit for deflate operations
1359 - improvements in SSL code nonblocking operation, possible hang solved,
1360 some SSL operations broken down into pollable states so there is
1361 no library blocking, timeout coverage for SSL_connect
1363 - extpoll test server merged into single test server source
1365 - robustness: library should deal with all recoverable socket conditions
1367 - rx flowcontrol for backpressure notification fixed and implmeneted
1368 correctly in the test server
1370 - optimal lexical parser added for header processing; all headers in a
1371 single 276-byte state table
1373 - latency tracking api added (configure --with-latency)
1375 - Improved in-tree documentation, REAME.build, README.coding,
1376 README.test-apps, changelog
1381 v1.0-chrome25-firefox17 (6cd1ea9b005933f)