Simple, secure & standards compliant web server for the most demanding of applications
APACHE-2.0 License
Bot releases are hidden (Show)
Published by uNetworkingAB 7 months ago
Previous release did not fix all problems with, for instance, underscores in HTTP field names. This release properly fixes such cases and also makes the HTTP server 14% faster in user space.
A new benchmarking project has been added for reliably benchmarking the entire user space portion of the server by overriding epoll syscalls with traffic producing alternatives. This is a similar approach to how we currently fuzz the user space.
Published by uNetworkingAB 8 months ago
A misinterpretation of the spec. has been fixed re. HTTP field names. If you rely on field names that aren't just alphanum + hyphen, this release should fix your use.
Published by uNetworkingAB 9 months ago
Having multiple URL routes with differently named parameter segments at the same depth in the routing tree would cause the order of matching to be potentially different from what the documentation stated.
This release fixes that, and adds more testing for this scenario.
Published by uNetworkingAB 9 months ago
We've always supported multi-CPU scaling as detailed in the HelloWorldThreaded.cpp
example and benchmarking blog posts. However, this example has only been properly supported on Linux systems and contained some really ugly boiler plate code.
This release adds the uWS::LocalCluster
helper that works properly on Windows, macOS, Linux and makes it easy to take any single-CPU app and make it scale over all available CPU-cores by default:
uWS::App(options).get(pattern, handler).listen(port, handler).run();
simply becomes
uWS::LocalCluster(options, [](uWS::App &app) {
app.get(pattern, handler).listen(port, handler);
});
This is reflected in the updated HelloWorldThreaded.cpp example and works for both SSL and non-SSL clusters.
Published by uNetworkingAB 9 months ago
Published by uNetworkingAB 10 months ago
/* Define a parameter route */
.get("/:first/static/:second", [](auto *res, auto *req) {
/* Use the value of a parameter as response */
res->write("<h1>first is: ");
res->write(req->getParameter("first"));
res->write("</h1>");
res->write("<h1>second is: ");
res->write(req->getParameter("second"));
res->end("</h1>");
})
Published by uNetworkingAB 10 months ago
Published by uNetworkingAB 10 months ago
Published by uNetworkingAB 10 months ago
Published by uNetworkingAB 10 months ago
The 404 page is no longer a static error page that severs the connection, but now lives as a default route for App.any("/*")
. This means two things:
App.any("/*", nullptr)
or attach your own page to that route.Published by uNetworkingAB 10 months ago
The ANY method (App::any) will now properly match with all possible HTTP methods, not just all of the standard ones. This is needed to properly implement your own (reliable) 404 page, or to reliably route all traffic to some common handler (what Bun does).
A slight behavioral change was needed:
This behavioral change should be practically unnoticeable.
More:
Published by uNetworkingAB 10 months ago
A new kind of event, "dropped" can be used to track when an outgoing message has been dropped due to current backpressure settings. This is useful in cases where tracking the status is otherwise impossible, such as when using pub/sub. See example "EchoServer.cpp" for usage.
Another change is the removal of graphical error pages (the HTML body is gone) when compiling with UWS_HTTPRESPONSE_NO_WRITEMARK.
Published by uNetworkingAB 11 months ago
Being subscribed to only one topic, followed by a publish to said topic immediately followed by unsubscription from this, single one, topic would drop the published message before it was sent. This is now fixed and no message will be dropped in this edge case.
This bug did not trigger in cases where a WebSocket was subscribed to at least one more topic, making most real-world use cases unaffected.
Full Changelog: https://github.com/uNetworking/uWebSockets/compare/v20.47.0...v20.48.0
Published by uNetworkingAB about 1 year ago
Full Changelog: https://github.com/uNetworking/uWebSockets/compare/v20.46.0...v20.47.0
Published by uNetworkingAB about 1 year ago
Full Changelog: https://github.com/uNetworking/uWebSockets/compare/v20.45.0...v20.46.0
Published by uNetworkingAB over 1 year ago
This release adds another error page; the 404 File Not Found. Along with the recently added error codes, this should make it a lot easier to debug proxy issues / log misbehaving clients or the like.
Instead of simply getting a RST (which often times results in 502), proxies and end clients now get the proper 404 error code for any unhandled URL / method.
This new behavior can be tested by running the EchoServer example and requesting any HTTP page.
Published by uNetworkingAB over 1 year ago
NGINX is a silly proxy. It's very common for users to report issues with NGINX, and it's easy to understand. If you set up NGINX as proxy for uWS, you will most likely get a spinning wheel followed by 502 Bad Gateway as if the uWS server is unreachable.
This is because NGINX defaults to the 27 year old, ancient, HTTP/1.0 when talking to backend servers. uWS naturally does not support this protocol, and is only fully standards compliant with the 26 years younger HTTP/1.1 RFC9112.
However, ideology aside, it would be nice if uWS played along with existing ecosystems. Now it does:
This page is what you will see after setting up NGINX to proxy uWS. From this error it should hint of the proxy_http_version 1.1 config in NGINX. Once applied, the NGINX -> uWS combo will give you this:
You can see and configure the error pages in src/HttpErrors.h. More errors will be added as they are needed. The default style is a minimal Apache-like page.
Published by uNetworkingAB over 1 year ago