7 1) There is now a "permessage-deflate" / RFC7692 implementation. It's very
8 similar to "deflate-frame" we have offered for a long while; deflate-frame is
9 now provided as an alias of permessage-deflate.
11 The main differences are that the new permessage-deflate implementation:
13 - properly performs streaming respecting input and output buffer limits. The
14 old deflate-frame implementation could only work on complete deflate input
15 and produce complete inflate output for each frame. The new implementation
16 only mallocs buffers at initialization.
18 - goes around the event loop after each input package is processed allowing
19 interleaved output processing. The RX flow control api can be used to
20 force compressed input processing to match the rate of compressed output
21 processing (test--echo shows an example of how to do this).
23 - when being "deflate-frame" for compatibility he uses the same default zlib
24 settings as the old "deflate-frame", but instead of exponentially increasing
25 malloc allocations until the whole output will fit, he observes the default
26 input and output chunking buffer sizes of "permessage-deflate", that's
27 1024 in and 1024 out at a time.
29 2) deflate-stream has been disabled for many versions (for over a year) and is
30 now removed. Browsers are now standardizing on "permessage-deflate" / RFC7692
32 3) struct lws_extension is simplified, and lws extensions now have a public
33 api (their callback) for use in user code to compose extensions and options
34 the user code wants. lws_get_internal_exts() is deprecated but kept around
35 as a NOP. The changes allow one extension implementation to go by different
36 names and allows the user client code to control option offers per-ext.
38 The test client and server are updated to use the new way. If you use
39 the old way it should still work, but extensions will be disabled until you
42 Extensions are now responsible for allocating and per-instance private struct
43 at instance construction time and freeing it when the instance is destroyed.
44 Not needing to know the size means the extension's struct can be opaque
51 1) The info struct gained two new members
53 - max_http_header_data: 0 for default (1024) or set the maximum amount of known
54 http header payload that lws can deal with. Payload in unknown http
55 headers is dropped silently. If for some reason you need to send huge
56 cookies or other HTTP-level headers, you can now increase this at context-
59 - max_http_header_pool: 0 for default (16) or set the maximum amount of http
60 headers that can be tracked by lws in this context. For the server, if
61 the header pool is completely in use then accepts on the listen socket
62 are disabled until one becomes free. For the client, if you simultaneously
63 have pending connects for more than this number of client connections,
64 additional connects will fail until some of the pending connections timeout
67 HTTP header processing in lws only exists until just after the first main
68 callback after the HTTP handshake... for ws connections that is ESTABLISHED and
69 for HTTP connections the HTTP callback.
71 So these settings are not related to the maximum number of simultaneous
72 connections, but the number of HTTP handshakes that may be expected or ongoing,
73 or have just completed, at one time. The reason it's useful is it changes the
74 memory allocation for header processing to be one-time at context creation
75 instead of every time there is a new connection, and gives you control over
78 Setting max_http_header_pool to 1 is fine it will just queue incoming
79 connections before the accept as necessary, you can still have as many
80 simultaneous post-header connections as you like. Since the http header
81 processing is completed and the allocation released after ESTABLISHED or the
82 HTTP callback, even with a pool of 1 many connections can be handled rapidly.
84 2) There is a new callback that allows the user code to get acccess to the
85 optional close code + aux data that may have been sent by the peer.
87 LWS_CALLBACK_WS_PEER_INITIATED_CLOSE:
88 The peer has sent an unsolicited Close WS packet. @in and
89 @len are the optional close code (first 2 bytes, network
90 order) and the optional additional information which is not
91 defined in the standard, and may be a string or non-human-
93 If you return 0 lws will echo the close and then close the
94 connection. If you return nonzero lws will just close the
97 As usual not handling it does the right thing, if you're not interested in it
100 The test server has "open and close" testing buttons at the bottom, if you
101 open and close that connection, on close it will send a close code 3000 decimal
102 and the string "Bye!" as the aux data.
104 The test server dumb-increment callback handles this callback reason and prints
106 lwsts[15714]: LWS_CALLBACK_WS_PEER_INITIATED_CLOSE: len 6
107 lwsts[15714]: 0: 0x0B
108 lwsts[15714]: 1: 0xB8
109 lwsts[15714]: 2: 0x42
110 lwsts[15714]: 3: 0x79
111 lwsts[15714]: 4: 0x65
112 lwsts[15714]: 5: 0x21
114 3) There is a new API to allow the user code to control the content of the
115 close frame sent when about to return nonzero from the user callback to
116 indicate the connection should close.
119 * lws_close_reason - Set reason and aux data to send with Close packet
120 * If you are going to return nonzero from the callback
121 * requesting the connection to close, you can optionally
122 * call this to set the reason the peer will be told if
125 * @wsi: The websocket connection to set the close reason on
126 * @status: A valid close status from websocket standard
127 * @buf: NULL or buffer containing up to 124 bytes of auxiliary data
128 * @len: Length of data in @buf to send
130 LWS_VISIBLE LWS_EXTERN void
131 lws_close_reason(struct lws *wsi, enum lws_close_status status,
132 unsigned char *buf, size_t len);
134 An extra button is added to the "open and close" test server page that requests
135 that the test server close the connection from his end.
137 The test server code will do so by
139 lws_close_reason(wsi, LWS_CLOSE_STATUS_GOINGAWAY,
140 (unsigned char *)"seeya", 5);
143 The browser shows the close code and reason he received
145 websocket connection CLOSED, code: 1001, reason: seeya
147 4) There's a new context creation time option flag
149 LWS_SERVER_OPTION_VALIDATE_UTF8
151 if you set it in info->options, then TEXT and CLOSE frames will get checked to
152 confirm that they contain valid UTF-8. If they don't, the connection will get
155 5) ECDH Certs are now supported. Enable the CMake option
157 cmake .. -DLWS_SSL_SERVER_WITH_ECDH_CERT=1
159 **and** the info->options flag
161 LWS_SERVER_OPTION_SSL_ECD
163 to build in support and select it at runtime.
165 6) There's a new api lws_parse_uri() that simplies chopping up
166 https://xxx:yyy/zzz uris into parts nicely. The test client now uses this
167 to allow proper uris as well as the old address style.
169 7) SMP support is integrated into LWS without any internal threading. It's
170 very simple to use, libwebsockets-test-server-pthread shows how to do it,
171 use -j <n> argument there to control the number of service threads up to 32.
173 Two new members are added to the info struct
175 unsigned int count_threads;
176 unsigned int fd_limit_per_thread;
178 leave them at the default 0 to get the normal singlethreaded service loop.
180 Set count_threads to n to tell lws you will have n simultaneous service threads
181 operating on the context.
183 There is still a single listen socket on one port, no matter how many
186 When a connection is made, it is accepted by the service thread with the least
187 connections active to perform load balancing.
189 The user code is responsible for spawning n threads running the service loop
190 associated to a specific tsi (Thread Service Index, 0 .. n - 1). See
191 the libwebsockets-test-server-pthread for how to do.
193 If you leave fd_limit_per_thread at 0, then the process limit of fds is shared
194 between the service threads; if you process was allowed 1024 fds overall then
195 each thread is limited to 1024 / n.
197 You can set fd_limit_per_thread to a nonzero number to control this manually, eg
198 the overall supported fd limit is less than the process allowance.
200 You can control the context basic data allocation for multithreading from Cmake
201 using -DLWS_MAX_SMP=, if not given it's set to 32. The serv_buf allocation
202 for the threads (currently 4096) is made at runtime only for active threads.
204 Because lws will limit the requested number of actual threads supported
205 according to LWS_MAX_SMP, there is an api lws_get_count_threads(context) to
206 discover how many threads were actually allowed when the context was created.
208 It's required to implement locking in the user code in the same way that
209 libwebsockets-test-server-pthread does it, for the FD locking callbacks.
211 If LWS_MAX_SMP=1, then there is no code related to pthreads compiled in the
212 library. If more than 1, a small amount of pthread mutex code is built into
217 LWS_VISIBLE struct lws *
218 lws_adopt_socket(struct lws_context *context, lws_sockfd_type accept_fd)
220 allows foreign sockets accepted by non-lws code to be adopted by lws as if they
221 had just been accepted by lws' own listen socket.
226 1) LWS_SEND_BUFFER_POST_PADDING is now 0 and deprecated. You can remove it; if
227 you still use it, obviously it does nothing. Old binary code with nonzero
228 LWS_SEND_BUFFER_POST_PADDING is perfectly compatible, the old code just
229 allocated a buffer bigger than the library is going to use.
231 The example apps no longer use LWS_SEND_BUFFER_POST_PADDING.
233 The only path who made use of it was sending with LWS_WRITE_CLOSE --->
235 2) Because of lws_close_reason() formalizing handling close frames,
236 LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send
237 close frames...close frame content should be managed using lws_close_reason()
240 3) We check for invalid CLOSE codes and complain about protocol violation in
241 our close code. But it changes little since we were in the middle of closing
244 4) zero-length RX frames and zero length TX frames are now allowed.
246 5) Pings and close used to be limited to 124 bytes, the correct limit is 125
247 so that is now also allowed.
249 6) LWS_PRE is provided as a synonym for LWS_SEND_BUFFER_POST_PADDING, either is
252 7) There's generic support for RFC7462 style extension options built into the
253 library now. As a consequence, a field "options" is added to lws_extension.
254 It can be NULL if there are no options on the extension. Extension internal
255 info is part of the public abi because extensions may be implemented outside
259 v1.6.0-chrome48-firefox42
260 =======================
262 Major API improvements
263 ----------------------
265 v1.6.0 has many cleanups and improvements in the API. Although at first it
266 looks pretty drastic, user code will only need four actions to update it.
268 - Do the three search/replaces in your user code, /libwebsocket_/lws_/,
269 /libwebsockets_/lws_/, and /struct\ libwebsocket/struct\ lws/
271 - Remove the context parameter from your user callbacks
273 - Remove context as the first parameter from the "Eleven APIS" listed in the
274 User Api Changes section
276 - Add lws_get_context(wsi) as the first parameter on the "Three APIS" listed
277 in the User Api Changes section, and anywhere else you still need context
279 That's it... generally only a handful of the 14 affected APIs are actually in
280 use in your user code and you can find them quickest by compiling and visiting
281 the errors each in turn. And the end results are much cleaner, more
282 predictable and maintainable.
288 1) lws now exposes his internal platform file abstraction in a way that can be
289 both used by user code to make it platform-agnostic, and be overridden or
290 subclassed by user code. This allows things like handling the URI "directory
291 space" as a virtual filesystem that may or may not be backed by a regular
292 filesystem. One example use is serving files from inside large compressed
293 archive storage without having to unpack anything except the file being
296 The test server shows how to use it, basically the platform-specific part of
297 lws prepares a file operations structure that lives in the lws context.
299 Helpers are provided to also leverage these platform-independent file handling
302 static inline lws_filefd_type
303 lws_plat_file_open(struct lws *wsi, const char *filename,
304 unsigned long *filelen, int flags)
306 lws_plat_file_close(struct lws *wsi, lws_filefd_type fd)
308 static inline unsigned long
309 lws_plat_file_seek_cur(struct lws *wsi, lws_filefd_type fd, long offset)
312 lws_plat_file_read(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
313 unsigned char *buf, unsigned long len)
316 lws_plat_file_write(struct lws *wsi, lws_filefd_type fd, unsigned long *amount,
317 unsigned char *buf, unsigned long len)
319 The user code can also override or subclass the file operations, to either
320 wrap or replace them. An example is shown in test server.
322 A wsi can be associated with the file activity, allowing per-connection
323 authentication and state to be used when interpreting the file request.
325 2) A new API void * lws_wsi_user(struct lws *wsi) lets you get the pointer to
326 the user data associated with the wsi, just from the wsi.
328 3) URI argument handling. Libwebsockets parses and protects URI arguments
329 like test.html?arg1=1&arg2=2, it decodes %xx uriencoding format and reduces
330 path attacks like ../.../../etc/passwd so they cannot go behind the web
331 server's /. There is a list of confirmed attacks we're proof against in
332 ./test-server/attack.sh.
334 There is a new API lws_hdr_copy_fragment that should be used now to access
335 the URI arguments (it returns the fragments length)
337 while (lws_hdr_copy_fragment(wsi, buf, sizeof(buf),
338 WSI_TOKEN_HTTP_URI_ARGS, n) > 0) {
339 lwsl_info("URI Arg %d: %s\n", ++n, buf);
342 For the example above, calling with n=0 will return "arg1=1" and n=1 "arg2=2".
343 All legal uriencodings will have been reduced in those strings.
345 lws_hdr_copy_fragment() returns the length of the x=y fragment, so it's also
346 possible to deal with arguments containing %00. If you don't care about that,
347 the returned string has '\0' appended to simplify processing.
355 - lws_callback_on_writable_all_protocol(const struct lws_protocols *protocol)
356 - lws_callback_all_protocol(const struct lws_protocols *protocol)
357 - lws_rx_flow_allow_all_protocol(lws_rx_flow_allow_all_protocol)
359 Now take an additional pointer to the lws_context in their first argument.
361 The reason for this change is struct lws_protocols has been changed to remove
362 members that lws used for private storage: so the protocols struct in now
363 truly const and may be reused serially or simultaneously by different contexts.
367 LWS_VISIBLE LWS_EXTERN int
368 lws_add_http_header_by_name(struct lws_context *context,
370 const unsigned char *name,
371 const unsigned char *value,
375 LWS_VISIBLE LWS_EXTERN int
376 lws_finalize_http_header(struct lws_context *context,
380 LWS_VISIBLE LWS_EXTERN int
381 lws_add_http_header_by_token(struct lws_context *context,
383 enum lws_token_indexes token,
384 const unsigned char *value,
388 LWS_VISIBLE LWS_EXTERN int
389 lws_add_http_header_content_length(struct lws_context *context,
391 unsigned long content_length,
394 LWS_VISIBLE LWS_EXTERN int
395 lws_add_http_header_status(struct lws_context *context, struct lws *wsi,
396 unsigned int code, unsigned char **p,
399 LWS_VISIBLE LWS_EXTERN int
400 lws_serve_http_file(struct lws_context *context, struct lws *wsi,
401 const char *file, const char *content_type,
402 const char *other_headers, int other_headers_len);
403 LWS_VISIBLE LWS_EXTERN int
404 lws_serve_http_file_fragment(struct lws_context *context, struct lws *wsi);
406 LWS_VISIBLE LWS_EXTERN int
407 lws_return_http_status(struct lws_context *context, struct lws *wsi,
408 unsigned int code, const char *html_body);
410 LWS_VISIBLE LWS_EXTERN int
411 lws_callback_on_writable(const struct lws_context *context, struct lws *wsi);
413 LWS_VISIBLE LWS_EXTERN void
414 lws_get_peer_addresses(struct lws_context *context, struct lws *wsi,
415 lws_sockfd_type fd, char *name, int name_len,
416 char *rip, int rip_len);
418 LWS_VISIBLE LWS_EXTERN int
419 lws_read(struct lws_context *context, struct lws *wsi,
420 unsigned char *buf, size_t len);
422 no longer require their initial struct lws_context * parameter.
424 3) Several older apis start with libwebsocket_ or libwebsockets_ while newer ones
425 all begin lws_. These apis have been changed to all begin with lws_.
427 To convert, search-replace
429 - libwebsockets_/lws_
431 - struct\ libwebsocket/struct\ lws
433 4) context parameter removed from user callback.
435 Since almost all apis no longer need the context as a parameter, it's no longer
436 provided at the user callback directly.
438 However if you need it, for ALL callbacks wsi is valid and has a valid context
439 pointer you can recover using lws_get_context(wsi).
442 v1.5-chrome47-firefox41
443 =======================
448 LWS_CALLBACK_CLIENT_CONNECTION_ERROR may provide an error string if in is
449 non-NULL. If so, the string has length len.
451 LWS_SERVER_OPTION_PEER_CERT_NOT_REQUIRED is available to relax the requirement
452 for peer certs if you are using the option to require client certs.
454 LWS_WITHOUT_BUILTIN_SHA1 cmake option forces lws to use SHA1() defined
455 externally, eg, byOpenSSL, and disables build of libwebsockets_SHA1()
458 v1.4-chrome43-firefox36
459 =======================
464 There's a new member in the info struct used to control context creation,
465 ssl_private_key_password, which allows passing into lws the passphrase on
468 There's a new member in struct protocols, id, which is ignored by lws but can
469 be used by the user code to mark the selected protocol by user-defined version
470 or capabliity flag information, for the case multiple versions of a protocol are
473 int lws_is_ssl(wsi) added to allow user code to know if the connection was made
474 over ssl or not. If LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT is used, both
475 ssl and non-ssl connections are possible and may need to be treated differently
478 int lws_partial_buffered(wsi) added... should be checked after any
479 libwebsocket_write that will be followed by another libwebsocket_write inside
480 the same writeable callback. If set, you can't do any more writes until the
481 writeable callback is called again. If you only do one write per writeable callback,
484 HTTP2-related: HTTP2 changes how headers are handled, lws now has new version-
485 agnositic header creation APIs. These do the right thing depending on each
486 connection's HTTP version without the user code having to know or care, except
487 to make sure to use the new APIs for headers (test-server is updated to use
488 them already, so look there for examples)
490 The APIs "render" the headers into a user-provided buffer and bump *p as it
491 is used. If *p reaches end, then the APIs return nonzero for error.
493 LWS_VISIBLE LWS_EXTERN int
494 lws_add_http_header_status(struct libwebsocket_context *context,
495 struct libwebsocket *wsi,
500 Start a response header reporting status like 200, 500, etc
502 LWS_VISIBLE LWS_EXTERN int
503 lws_add_http_header_by_name(struct libwebsocket_context *context,
504 struct libwebsocket *wsi,
505 const unsigned char *name,
506 const unsigned char *value,
511 Add a header like name: value in HTTP1.x
513 LWS_VISIBLE LWS_EXTERN int
514 lws_finalize_http_header(struct libwebsocket_context *context,
515 struct libwebsocket *wsi,
519 Finish off the headers, like add the extra \r\n in HTTP1.x
521 LWS_VISIBLE LWS_EXTERN int
522 lws_add_http_header_by_token(struct libwebsocket_context *context,
523 struct libwebsocket *wsi,
524 enum lws_token_indexes token,
525 const unsigned char *value,
530 Add a header by using a lws token as the name part. In HTTP2, this can be
531 compressed to one or two bytes.
537 protocols struct member no_buffer_all_partial_tx is removed. Under some
538 conditions like rewriting extension such as compression in use, the built-in
539 partial send buffering is the only way to deal with the problem, so turning
540 it off is deprecated.
546 HTTP2-related: API libwebsockets_serve_http_file() takes an extra parameter at
549 int other_headers_len)
551 If you are providing other headers, they must be generated using the new
552 HTTP-version-agnostic APIs, and you must provide the length of them using this
553 additional parameter.
555 struct lws_context_creation_info now has an additional member
556 SSL_CTX *provided_client_ssl_ctx you may set to an externally-initialized
557 SSL_CTX managed outside lws. Defaulting to zero keeps the existing behaviour of
558 lws managing the context, if you memset the struct to 0 or have as a filescope
559 initialized struct in bss, no need to change anything.
562 v1.3-chrome37-firefox30
563 =======================
566 CMakeLists.txt | 447 +++--
570 cmake/LibwebsocketsConfig.cmake.in | 17 +
571 cmake/LibwebsocketsConfigVersion.cmake.in | 11 +
572 config.h.cmake | 18 +
573 cross-ming.cmake | 31 +
574 cross-openwrt-makefile | 91 +
575 lib/client-handshake.c | 205 ++-
576 lib/client-parser.c | 58 +-
577 lib/client.c | 158 +-
578 lib/context.c | 341 ++++
579 lib/extension-deflate-frame.c | 2 +-
580 lib/extension.c | 178 ++
581 lib/handshake.c | 287 +---
582 lib/lextable.h | 338 ++++
584 lib/libwebsockets.c | 2089 +++--------------------
585 lib/libwebsockets.h | 253 ++-
586 lib/lws-plat-unix.c | 404 +++++
587 lib/lws-plat-win.c | 358 ++++
588 lib/minilex.c | 530 +++---
589 lib/output.c | 445 ++---
590 lib/parsers.c | 682 ++++----
591 lib/pollfd.c | 239 +++
592 lib/private-libwebsockets.h | 501 +++++-
593 lib/server-handshake.c | 274 +--
594 lib/server.c | 858 ++++++++--
595 lib/service.c | 517 ++++++
597 lib/ssl-http2.c | 78 +
598 lib/ssl.c | 571 +++++++
599 test-server/attack.sh | 101 +-
600 test-server/test-client.c | 9 +-
601 test-server/test-echo.c | 17 +-
602 test-server/test-fraggle.c | 7 -
603 test-server/test-ping.c | 12 +-
604 test-server/test-server.c | 330 ++--
605 test-server/test.html | 4 +-
606 win32port/client/client.vcxproj | 259 ---
607 win32port/client/client.vcxproj.filters | 39 -
608 .../libwebsocketswin32.vcxproj.filters | 93 -
609 win32port/server/server.vcxproj | 276 ---
610 win32port/server/server.vcxproj.filters | 51 -
611 win32port/win32helpers/gettimeofday.h | 59 +-
612 win32port/win32helpers/netdb.h | 1 -
613 win32port/win32helpers/strings.h | 0
614 win32port/win32helpers/sys/time.h | 1 -
615 win32port/win32helpers/unistd.h | 0
616 win32port/win32helpers/websock-w32.c | 104 --
617 win32port/win32helpers/websock-w32.h | 62 -
618 win32port/win32port.sln | 100 --
619 win32port/zlib/gzio.c | 3 +-
620 55 files changed, 6779 insertions(+), 5059 deletions(-)
626 POST method is supported
628 The protocol 0 / HTTP callback can now get two new kinds of callback,
629 LWS_CALLBACK_HTTP_BODY (in and len are a chunk of the body of the HTTP request)
630 and LWS_CALLBACK_HTTP_BODY_COMPLETION (the expected amount of body has arrived
631 and been passed to the user code already). These callbacks are used with the
632 post method (see the test server for details).
634 The period between the HTTP header completion and the completion of the body
635 processing is protected by a 5s timeout.
637 The chunks are stored in a malloc'd buffer of size protocols[0].rx_buffer_size.
640 New server option you can enable from user code
641 LWS_SERVER_OPTION_ALLOW_NON_SSL_ON_SSL_PORT allows non-SSL connections to
642 also be accepted on an SSL listening port. It's disabled unless you enable
646 Two new callbacks are added in protocols[0] that are optional for allowing
647 limited thread access to libwebsockets, LWS_CALLBACK_LOCK_POLL and
648 LWS_CALLBACK_UNLOCK_POLL.
650 If you use them, they protect internal and external poll list changes, but if
651 you want to use external thread access to libwebsocket_callback_on_writable()
652 you have to implement your locking here even if you don't use external
655 If you will use another thread for this, take a lot of care about managing
656 your list of live wsi by doing it from ESTABLISHED and CLOSED callbacks
657 (with your own locking).
659 If you configure cmake with -DLWS_WITH_LIBEV=1 then the code allowing the libev
660 eventloop instead of the default poll() one will also be compiled in. But to
661 use it, you must also set the LWS_SERVER_OPTION_LIBEV flag on the context
662 creation info struct options member.
664 IPV6 is supported and enabled by default except for Windows, you can disable
665 the support at build-time by giving -DLWS_IPV6=, and disable use of it even if
666 compiled in by making sure the flag LWS_SERVER_OPTION_DISABLE_IPV6 is set on
667 the context creation info struct options member.
669 You can give LWS_SERVER_OPTION_DISABLE_OS_CA_CERTS option flag to
670 guarantee the OS CAs will not be used, even if that support was selected at
673 Optional "token limits" may be enforced by setting the member "token_limits"
674 in struct lws_context_creation_info to point to a struct lws_token_limits.
675 NULL means no token limits used for compatibility.
681 Extra optional argument to libwebsockets_serve_http_file() allows injecion
682 of HTTP headers into the canned response. Eg, cookies may be added like
683 that without getting involved in having to send the header by hand.
685 A new info member http_proxy_address may be used at context creation time to
686 set the http proxy. If non-NULL, it overrides http_proxy environment var.
688 Cmake supports LWS_SSL_CLIENT_USE_OS_CA_CERTS defaulting to on, which gets
689 the client to use the OS CA Roots. If you're worried somebody with the
690 ability to forge for force creation of a client cert from the root CA in
691 your OS, you should disable this since your selfsigned $0 cert is a lot safer
695 v1.23-chrome32-firefox24
696 ========================
699 CMakeLists.txt | 573 ++++++++----
700 COPYING | 503 -----------
701 INSTALL | 365 --------
703 README.build | 371 ++------
704 README.coding | 63 ++
705 autogen.sh | 1578 ---------------------------------
707 cmake/FindGit.cmake | 163 ++++
708 cmake/FindOpenSSLbins.cmake | 15 +-
709 cmake/UseRPMTools.cmake | 176 ++++
710 config.h.cmake | 25 +-
711 configure.ac | 226 -----
712 cross-arm-linux-gnueabihf.cmake | 28 +
713 lib/Makefile.am | 89 --
714 lib/base64-decode.c | 98 +-
715 lib/client-handshake.c | 123 ++-
716 lib/client-parser.c | 19 +-
717 lib/client.c | 145 ++-
718 lib/daemonize.c | 4 +-
719 lib/extension.c | 2 +-
720 lib/getifaddrs.h | 4 +-
721 lib/handshake.c | 76 +-
722 lib/libwebsockets.c | 491 ++++++----
723 lib/libwebsockets.h | 164 ++--
724 lib/output.c | 214 ++++-
725 lib/parsers.c | 102 +--
726 lib/private-libwebsockets.h | 66 +-
727 lib/server-handshake.c | 5 +-
730 libwebsockets-api-doc.html | 249 +++---
731 libwebsockets.pc.in | 11 -
732 libwebsockets.spec | 14 +-
734 scripts/FindLibWebSockets.cmake | 33 +
735 scripts/kernel-doc | 1 +
736 test-server/Makefile.am | 131 ---
737 test-server/leaf.jpg | Bin 0 -> 2477518 bytes
738 test-server/test-client.c | 78 +-
739 test-server/test-echo.c | 33 +-
740 test-server/test-fraggle.c | 26 +-
741 test-server/test-ping.c | 15 +-
742 test-server/test-server.c | 197 +++-
743 test-server/test.html | 5 +-
744 win32port/win32helpers/gettimeofday.c | 74 +-
745 win32port/win32helpers/websock-w32.h | 6 +-
746 48 files changed, 2493 insertions(+), 4212 deletions(-)
752 - You can now call libwebsocket_callback_on_writable() on http connectons,
753 and get a LWS_CALLBACK_HTTP_WRITEABLE callback, the same way you can
754 regulate writes with a websocket protocol connection.
756 - A new member in the context creation parameter struct "ssl_cipher_list" is
757 added, replacing CIPHERS_LIST_STRING. NULL means use the ssl library
758 default list of ciphers.
760 - Not really an api addition, but libwebsocket_service_fd() will now zero
761 the revents field of the pollfd it was called with if it handled the
762 descriptor. So you can tell if it is a non-lws fd by checking revents
763 after the service call... if it's still nonzero, the descriptor
764 belongs to you and you need to take care of it.
766 - libwebsocket_rx_flow_allow_all_protocol(protocol) will unthrottle all
767 connections with the established protocol. It's designed to be
768 called from user server code when it sees it can accept more input
769 and may have throttled connections using the server rx flow apis
770 while it was unable to accept any other input The user server code
771 then does not have to try to track while connections it choked, this
772 will free up all of them in one call.
774 - there's a new, optional callback LWS_CALLBACK_CLOSED_HTTP which gets
775 called when an HTTP protocol socket closes
777 - for LWS_CALLBACK_FILTER_PROTOCOL_CONNECTION callback, the user_space alloc
778 has already been done before the callback happens. That means we can
779 use the user parameter to the callback to contain the user pointer, and
780 move the protocol name to the "in" parameter. The docs for this
781 callback are also updated to reflect how to check headers in there.
783 - libwebsocket_client_connect() is now properly nonblocking and async. See
784 README.coding and test-client.c for information on the callbacks you
785 can rely on controlling the async connection period with.
787 - if your OS does not support the http_proxy environment variable convention
788 (eg, reportedly OSX), you can use a new api libwebsocket_set_proxy()
789 to set the proxy details in between context creation and the connection
790 action. For OSes that support http_proxy, that's used automatically.
795 - the external poll callbacks now get the socket descriptor coming from the
796 "in" parameter. The user parameter provides the user_space for the
797 wsi as it normally does on the other callbacks.
798 LWS_CALLBACK_FILTER_NETWORK_CONNECTION also has the socket descriptor
799 delivered by @in now instead of @user.
801 - libwebsocket_write() now returns -1 for error, or the amount of data
802 actually accepted for send. Under load, the OS may signal it is
803 ready to send new data on the socket, but have only a restricted
804 amount of memory to buffer the packet compared to usual.
810 - libwebsocket_ensure_user_space() is removed from the public api, if you
811 were using it to get user_space, you need to adapt your code to only
812 use user_space inside the user callback.
814 - CIPHERS_LIST_STRING is removed
816 - autotools build has been removed. See README.build for info on how to
817 use CMake for your platform
820 v1.21-chrome26-firefox18
821 ========================
823 - Fixes buffer overflow bug in max frame size handling if you used the
824 default protocol buffer size. If you declared rx_buffer_size in your
825 protocol, which is recommended anyway, your code was unaffected.
827 v1.2-chrome26-firefox18
828 =======================
834 CMakeLists.txt | 544 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
835 LICENSE | 526 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
838 README.build | 258 ++++++++++++++++++++++++++++++++-----
839 README.coding | 52 ++++++++
840 changelog | 136 ++++++++++++++++++++
841 cmake/FindOpenSSLbins.cmake | 33 +++++
842 config.h.cmake | 173 +++++++++++++++++++++++++
843 configure.ac | 22 +++-
844 lib/Makefile.am | 20 ++-
845 lib/base64-decode.c | 2 +-
846 lib/client-handshake.c | 190 +++++++++++-----------------
847 lib/client-parser.c | 88 +++++++------
848 lib/client.c | 384 ++++++++++++++++++++++++++++++-------------------------
849 lib/daemonize.c | 32 +++--
850 lib/extension-deflate-frame.c | 58 +++++----
851 lib/extension-deflate-stream.c | 19 ++-
852 lib/extension-deflate-stream.h | 4 +-
853 lib/extension.c | 11 +-
854 lib/getifaddrs.c | 315 +++++++++++++++++++++++-----------------------
855 lib/getifaddrs.h | 30 ++---
856 lib/handshake.c | 124 +++++++++++-------
857 lib/libwebsockets.c | 736 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------
858 lib/libwebsockets.h | 237 ++++++++++++++++++++++------------
859 lib/output.c | 192 +++++++++++-----------------
860 lib/parsers.c | 966 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------
861 lib/private-libwebsockets.h | 225 +++++++++++++++++++++------------
862 lib/server-handshake.c | 82 ++++++------
863 lib/server.c | 96 +++++++-------
864 libwebsockets-api-doc.html | 189 ++++++++++++++++++----------
865 libwebsockets.spec | 17 +--
866 test-server/attack.sh | 148 ++++++++++++++++++++++
867 test-server/test-client.c | 125 +++++++++---------
868 test-server/test-echo.c | 31 +++--
869 test-server/test-fraggle.c | 32 ++---
870 test-server/test-ping.c | 52 ++++----
871 test-server/test-server.c | 129 ++++++++++++-------
872 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj | 279 ----------------------------------------
873 win32port/libwebsocketswin32/libwebsocketswin32.vcxproj.filters | 23 +++-
874 41 files changed, 4398 insertions(+), 2219 deletions(-)
880 - lws_get_library_version() returns a const char * with a string like
881 "1.1 9e7f737", representing the library version from configure.ac
882 and the git HEAD hash the library was built from
884 - TCP Keepalive can now optionally be applied to all lws sockets, on Linux
885 also with controllable timeout, number of probes and probe interval.
886 (On BSD type OS, you can only use system default settings for the
887 timing and retries, although enabling it is supported by setting
888 ka_time to nonzero, the exact value has no meaning.)
889 This enables detection of idle connections which are logically okay,
890 but are in fact dead, due to network connectivity issues at the server,
891 client, or any intermediary. By default it's not enabled, but you
892 can enable it by setting a non-zero timeout (in seconds) at the new
893 ka_time member at context creation time.
895 - Two new optional user callbacks added, LWS_CALLBACK_PROTOCOL_DESTROY which
896 is called one-time per protocol as the context is being destroyed, and
897 LWS_CALLBACK_PROTOCOL_INIT which is called when the context is created
898 and the protocols are added, again it's a one-time affair.
899 This lets you manage per-protocol allocations properly including
900 cleaning up after yourself when the server goes down.
905 - libwebsocket_create_context() has changed from taking a ton of parameters
906 to just taking a pointer to a struct containing the parameters. The
907 struct lws_context_creation_info is in libwebsockets.h, the members
908 are in the same order as when they were parameters to the call
909 previously. The test apps are all updated accordingly so you can
910 see example code there.
912 - Header tokens are now deleted after the websocket connection is
913 established. Not just the header data is saved, but the pointer and
914 length array is also removed from (union) scope saving several hundred
915 bytes per connection once it is established
917 - struct libwebsocket_protocols has a new member rx_buffer_size, this
918 controls rx buffer size per connection of that protocol now. Sources
919 for apps built against older versions of the library won't declare
920 this in their protocols, defaulting it to 0. Zero buffer is legal,
921 it causes a default buffer to be allocated (currently 4096)
923 If you want to receive only atomic frames in your user callback, you
924 should set this to greater than your largest frame size. If a frame
925 comes that exceeds that, no error occurs but the callback happens as
926 soon as the buffer limit is reached, and again if it is reached again
927 or the frame completes. You can detect that has happened by seeing
928 there is still frame content pending using
929 libwebsockets_remaining_packet_payload()
931 By correctly setting this, you can save a lot of memory when your
932 protocol has small frames (see the test server and client sources).
934 - LWS_MAX_HEADER_LEN now defaults to 1024 and is the total amount of known
935 header payload lws can cope with, that includes the GET URL, origin
936 etc. Headers not understood by lws are ignored and their payload
937 not included in this.
943 - The configuration-time option MAX_USER_RX_BUFFER has been replaced by a
944 buffer size chosen per-protocol. For compatibility, there's a default
945 of 4096 rx buffer, but user code should set the appropriate size for
948 - LWS_INITIAL_HDR_ALLOC and LWS_ADDITIONAL_HDR_ALLOC are no longer needed
949 and have been removed. There's a new header management scheme that
950 handles them in a much more compact way.
952 - libwebsockets_hangup_on_client() is removed. If you want to close the
953 connection you must do so from the user callback and by returning
956 - libwebsocket_close_and_free_session() is now private to the library code
957 only and not exposed for user code. If you want to close the
958 connection, you must do so from the user callback by returning -1
965 - Cmake project file added, aimed initially at Windows support: this replaces
966 the visual studio project files that were in the tree until now.
968 - CyaSSL now supported in place of OpenSSL (--use-cyassl on configure)
970 - PATH_MAX or MAX_PATH no longer needed
972 - cutomizable frame rx buffer size by protocol
974 - optional TCP keepalive so dead peers can be detected, can be enabled at
975 context-creation time
977 - valgrind-clean: no SSL or CyaSSL: completely clean. With OpenSSL, 88 bytes
978 lost at OpenSSL library init and symptomless reports of uninitialized
979 memory usage... seems to be a known and ignored problem at OpenSSL
981 - By default debug is enabled and the library is built for -O0 -g to faclitate
982 that. Use --disable-debug configure option to build instead with -O4
983 and no -g (debug info), obviously providing best performance and
986 - 1.0 introduced some code to try to not deflate small frames, however this
987 seems to break when confronted with a mixture of frames above and
988 below the threshold, so it's removed. Veto the compression extension
989 in your user callback if you will typically have very small frames.
991 - There are many memory usage improvements, both a reduction in malloc/
992 realloc and architectural changes. A websocket connection now
993 consumes only 296 bytes with SSL or 272 bytes without on x86_64,
994 during header processing an additional 1262 bytes is allocated in a
995 single malloc, but is freed when the websocket connection starts.
996 The RX frame buffer defined by the protocol in user
997 code is also allocated per connection, this represents the largest
998 frame you can receive atomically in that protocol.
1000 - On ARM9 build, just http+ws server no extensions or ssl, <12Kbytes .text
1001 and 112 bytes per connection (+1328 only during header processing)
1004 v1.1-chrome26-firefox18
1005 =======================
1011 README-test-server | 291 ---
1012 README.build | 239 ++
1013 README.coding | 138 ++
1015 README.test-apps | 272 +++
1016 configure.ac | 116 +-
1017 lib/Makefile.am | 55 +-
1018 lib/base64-decode.c | 5 +-
1019 lib/client-handshake.c | 121 +-
1020 lib/client-parser.c | 394 ++++
1021 lib/client.c | 807 +++++++
1022 lib/daemonize.c | 212 ++
1023 lib/extension-deflate-frame.c | 132 +-
1024 lib/extension-deflate-stream.c | 12 +-
1025 lib/extension-x-google-mux.c | 1223 ----------
1026 lib/extension-x-google-mux.h | 96 -
1027 lib/extension.c | 8 -
1028 lib/getifaddrs.c | 271 +++
1029 lib/getifaddrs.h | 76 +
1030 lib/handshake.c | 582 +----
1031 lib/libwebsockets.c | 2493 ++++++---------------
1032 lib/libwebsockets.h | 115 +-
1034 lib/minilex.c | 440 ++++
1035 lib/output.c | 628 ++++++
1036 lib/parsers.c | 2016 +++++------------
1037 lib/private-libwebsockets.h | 284 +--
1038 lib/server-handshake.c | 275 +++
1039 lib/server.c | 377 ++++
1040 libwebsockets-api-doc.html | 300 +--
1042 test-server/Makefile.am | 111 +-
1043 test-server/libwebsockets.org-logo.png | Bin 0 -> 7029 bytes
1044 test-server/test-client.c | 45 +-
1045 test-server/test-echo.c | 330 +++
1046 test-server/test-fraggle.c | 20 +-
1047 test-server/test-ping.c | 22 +-
1048 test-server/test-server-extpoll.c | 554 -----
1049 test-server/test-server.c | 349 ++-
1050 test-server/test.html | 3 +-
1051 win32port/zlib/ZLib.vcxproj | 749 ++++---
1052 win32port/zlib/ZLib.vcxproj.filters | 188 +-
1053 win32port/zlib/adler32.c | 348 ++-
1054 win32port/zlib/compress.c | 160 +-
1055 win32port/zlib/crc32.c | 867 ++++----
1056 win32port/zlib/crc32.h | 882 ++++----
1057 win32port/zlib/deflate.c | 3799 +++++++++++++++-----------------
1058 win32port/zlib/deflate.h | 688 +++---
1059 win32port/zlib/gzclose.c | 50 +-
1060 win32port/zlib/gzguts.h | 325 ++-
1061 win32port/zlib/gzlib.c | 1157 +++++-----
1062 win32port/zlib/gzread.c | 1242 ++++++-----
1063 win32port/zlib/gzwrite.c | 1096 +++++----
1064 win32port/zlib/infback.c | 1272 ++++++-----
1065 win32port/zlib/inffast.c | 680 +++---
1066 win32port/zlib/inffast.h | 22 +-
1067 win32port/zlib/inffixed.h | 188 +-
1068 win32port/zlib/inflate.c | 2976 +++++++++++++------------
1069 win32port/zlib/inflate.h | 244 +-
1070 win32port/zlib/inftrees.c | 636 +++---
1071 win32port/zlib/inftrees.h | 124 +-
1072 win32port/zlib/trees.c | 2468 +++++++++++----------
1073 win32port/zlib/trees.h | 256 +--
1074 win32port/zlib/uncompr.c | 118 +-
1075 win32port/zlib/zconf.h | 934 ++++----
1076 win32port/zlib/zlib.h | 3357 ++++++++++++++--------------
1077 win32port/zlib/zutil.c | 642 +++---
1078 win32port/zlib/zutil.h | 526 ++---
1079 69 files changed, 19556 insertions(+), 20145 deletions(-)
1084 - libwebsockets_serve_http_file() now takes a context as first argument
1086 - libwebsockets_get_peer_addresses() now takes a context and wsi as first
1093 - lwsl_...() logging apis, default to stderr but retargetable by user code;
1094 may be used also by user code
1096 - lws_set_log_level() set which logging apis are able to emit (defaults to
1097 notice, warn, err severities), optionally set the emit callback
1099 - lwsl_emit_syslog() helper callback emits to syslog
1101 - lws_daemonize() helper code that forks the app into a headless daemon
1102 properly, maintains a lock file with pid in suitable for sysvinit etc to
1105 - LWS_CALLBACK_HTTP_FILE_COMPLETION callback added since http file
1106 transfer is now asynchronous (see test server code)
1108 - lws_frame_is_binary() from a wsi pointer, let you know if the received
1109 data was sent in BINARY mode
1115 - libwebsockets_fork_service_loop() - no longer supported (had intractable problems)
1116 arrange your code to act from the user callback instead from same
1117 process context as the service loop
1119 - libwebsockets_broadcast() - use libwebsocket_callback_on_writable[_all_protocol]()
1120 instead from same process context as the service loop. See the test apps
1123 - x-google-mux() removed until someone wants it
1125 - pre -v13 (ancient) protocol support removed
1131 - echo test server and client compatible with echo.websocket.org added
1133 - many new configure options (see README.build) to reduce footprint of the
1134 library to what you actually need, eg, --without-client and
1137 - http + websocket server can build to as little as 12K .text for ARM
1139 - no more MAX_CLIENTS limitation; adapts to support the max number of fds
1140 allowed to the process by ulimit, defaults to 1024 on Fedora and
1141 Ubuntu. Use ulimit to control this without needing to configure
1142 the library. Code here is smaller and faster.
1144 - adaptive ratio of listen socket to connection socket service allows
1145 good behaviour under Apache ab test load. Tested with thousands
1146 of simultaneous connections
1148 - reduction in per-connection memory footprint by moving to a union to hold
1149 mutually-exclusive state for the connection
1151 - robustness: Out of Memory taken care of for all allocation code now
1153 - internal getifaddrs option if your toolchain lacks it (some uclibc)
1155 - configurable memory limit for deflate operations
1157 - improvements in SSL code nonblocking operation, possible hang solved,
1158 some SSL operations broken down into pollable states so there is
1159 no library blocking, timeout coverage for SSL_connect
1161 - extpoll test server merged into single test server source
1163 - robustness: library should deal with all recoverable socket conditions
1165 - rx flowcontrol for backpressure notification fixed and implmeneted
1166 correctly in the test server
1168 - optimal lexical parser added for header processing; all headers in a
1169 single 276-byte state table
1171 - latency tracking api added (configure --with-latency)
1173 - Improved in-tree documentation, REAME.build, README.coding,
1174 README.test-apps, changelog
1179 v1.0-chrome25-firefox17 (6cd1ea9b005933f)