Skip to content

LWT 3.2.1: First-boot database crash & reverse-proxy mixed-content fixes

Choose a tag to compare

View all tags
@HugoFara HugoFara released this 30 Jun 20:41
· 167 commits to main since this release
3.2.1
1b8e86b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release fixing two issues that surfaced since 3.2.0.

Fixed

  • Database error on first boot with CRLF schema files (#241). A fresh install could fail to start with "Internal Server Error - A database error occurred." (MySQL error 1064) while applying db/schema/baseline.sql. SqlFileParser split statements on ';' . PHP_EOL — which is ";\n" on a Linux host — so a schema file with Windows (CRLF) line endings was never split, and the whole file was sent to MySQL as a single multi-statement query that it rejected. The parser now normalizes CRLF/CR to LF before splitting, so parsing no longer depends on the file's origin OS.
  • Mixed-content asset blocking behind a TLS-terminating reverse proxy (#240). The Content-Security-Policy now emits upgrade-insecure-requests on HTTPS connections, so any stray http:// subresource is transparently upgraded to https:// instead of being blocked as mixed content — this is what left the language picker (and other scripts) unloaded on installs whose proxy doesn't propagate the scheme. The directive is omitted over plain HTTP so local development isn't forced to upgrade.

Full Changelog: 3.2.0...3.2.1

Assets 8
Loading