Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: MDA2AV/Http11Probe
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: MDA2AV/Http11Probe
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: add-uwebsockets-js
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 7 files changed
  • 1 contributor

Commits on Aug 15, 2026

  1. Add uWebSockets.js

    Requested upstream in uNetworking/uWebSockets.js#1298, where the maintainer
    asked to add uWS here and fix standards behaviour rather than chase
    benchmark lists.
    
    Implements the four probe endpoints with the idiomatic uWS API: any() routes
    with the wildcard registered last, req.forEach for /echo, and onData/onAborted
    with a cork()ed reply for the POST body echo. Header and cookie handling
    mirror the Node and Express servers so the three stay comparable.
    
    uWS is not on the npm registry, so the dependency is pinned to the v20.69.0
    release tarball — release tags carry prebuilt .node binaries, so no build
    step and no git in the image. The base image is node:22-trixie-slim rather
    than the usual node:22-slim because those binaries need glibc 2.38 or newer
    and bookworm ships 2.36; on bookworm the module fails to load at startup.
    MDA2AV committed Aug 15, 2026
    Configuration menu
    Copy the full SHA
    e5b7a5c View commit details
    Browse the repository at this point in the history
  2. Address SonarCloud findings on the uWS server

    Quality gate failed on Security Rating C for new code, from three major
    findings on the Dockerfile and one minor one.
    
    Add a generated package-lock.json and switch to npm ci, which pins the
    release tarball by sha512 integrity hash rather than trusting whatever the
    tag currently resolves to (docker:S8543, text:S8564). Pass --ignore-scripts;
    uWS declares no lifecycle scripts, so this costs nothing and closes the
    install-time execution path (docker:S6505). Run as the image's node user
    instead of root, matching Trillium, Effinitive, Horse and Swerver
    (docker:S6471) — port 8080 needs no privilege.
    
    .gitignore excluded every package-lock.json, which would have left the
    image building from an unpinned tarball in CI while working locally. Negate
    it for src/Servers so server locks are tracked; web/ is unaffected.
    
    Also Number.parseInt over the global (javascript:S7773).
    
    None of this touches HTTP behaviour: the suite scores 119/159 before and
    after, identical failure set.
    MDA2AV committed Aug 15, 2026
    Configuration menu
    Copy the full SHA
    77706a9 View commit details
    Browse the repository at this point in the history
Loading