Skip to content

fix: handle invalid static path encoding#36

Merged
ralyodio merged 1 commit into
profullstack:masterfrom
rissrice2105-agent:codex/handle-invalid-static-path-encoding
Jun 14, 2026
Merged

fix: handle invalid static path encoding#36
ralyodio merged 1 commit into
profullstack:masterfrom
rissrice2105-agent:codex/handle-invalid-static-path-encoding

Conversation

@rissrice2105-agent

Copy link
Copy Markdown
Contributor

Summary

  • catch malformed percent-encoded static paths in the CommandBoard PWA server
  • return 400 Invalid path encoding instead of allowing URIError to terminate the process
  • preserve normal API/health handling after the bad request

Closes #35

Testing

  • npm test
  • npm run build
  • manual server check: curl --path-as-is http://127.0.0.1:43173/% returns 400, then /health returns 200 and the process remains alive

npm run test:e2e --workspace @logicsrc/commandboard-web could not run because the local Playwright Chromium binary is not installed.

@ralyodio ralyodio merged commit 63ccad6 into profullstack:master Jun 14, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Malformed static path encoding crashes the CommandBoard PWA server

2 participants