Skip to content

fix(web): validate remote URLs and prevent private API caching (#313) - #318

Merged
pitill0 merged 1 commit into
mainfrom
fix/issue-313-api-cache-url-validation
Oct 30, 2026
Merged

pitill0 merged 1 commit into
mainfrom
fix/issue-313-api-cache-url-validation

Conversation

@pitill0

@pitill0 pitill0 commented Oct 30, 2026

Copy link
Copy Markdown
Owner

Summary

Closes #313.

Improve remote collection URL validation and prevent browser or intermediary caching of private Web API responses.

Changes

  • Reject unsupported remote collection URL schemes with HTTP 400 before initiating downloads.
  • Preserve HTTP 502 for genuine remote retrieval failures.
  • Retain the existing SSRF-protected transport.
  • Apply Cache-Control: no-store to private /api/ responses, including authentication and validation errors.
  • Preserve the existing cache behavior of public API endpoints and static resources.
  • Add regression tests and update the changelog.

Validation

  • 1,901 passed, 8 skipped.
  • Ruff lint and formatting passed.
  • Mypy passed.
  • Python compilation passed.
  • JavaScript syntax check passed.
  • Bandit reported no findings.
  • git diff --check passed.

The local dependency audit findings have been investigated separately; the remote CI dependency audit remains the release gate.

Deployment

No production changes have been made. The changes will take effect with a subsequent FluxTuner deployment.

@pitill0 pitill0 self-assigned this Oct 30, 2026
@pitill0
pitill0 merged commit 0798956 into main Oct 30, 2026
7 checks passed
@pitill0
pitill0 deleted the fix/issue-313-api-cache-url-validation branch October 30, 2026 21:50
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.

security(web): harden URL validation and private API cache policy

1 participant