Artifact [d37d496a7b]

Artifact d37d496a7bae0e30b6e964752cfa34115c2e889d0654747dc177810544b79901:

• File internal/sync/nethttp_std.go — part of check-in [9594cf3bae] at 2026-10-29 03:06:23 on branch main — perf(wasm): add a libfossil_nohttp build tag that leaves out net/http

  Under TinyGo, importing net/http at all links its TLS and X.509 code (crypto/x509, encoding/asn1, math/big's integers, AES-GCM, SHA-3, netip) whether or not a request is ever made: a five-line program that calls only http.StatusText grows by about 430 KB raw. The library imports it for its HTTP client transport and its HTTP server, which a program that serves sync through HandleSyncWithOpts and supplies its own transport never calls.

  Built with -tags libfossil_nohttp, the library leaves out NewHTTPTransport, WithHTTPClient, Repo.Pull, Repo.XferHandler and Repo.ServeHTTP, and the internal/sync client, server, redirect handling and peer-address trace they use. HandleSync, HandleSyncWithOpts, Sync over a host Transport and everything else are unchanged. Without the tag nothing changes. The retry classifier keeps the two statuses it read from net/http as constants, and DNS fault classification moves to its own file so it stays in the tagged build.

  For the html-artifact-publisher engine (TinyGo 0.43.0, Go 1.26.0) the tag takes the gzipped binary from 1,100,251 to 1,003,279 bytes. A test builds the library, db and simio with the tag for the host and js/wasm and checks none links net/http, net/http/httptrace or crypto/tls, and that the untagged library still does. (user: [email protected], size: 274) [annotate] [blame] [check-ins using] [more...]

//go:build !tinygo && !libfossil_nohttp

package sync

import "net/http"

// errStopRedirect makes the client hand back a redirect response instead of
// following it, so PostXfer applies the sync protocol's own redirect rules.
var errStopRedirect = http.ErrUseLastResponse