Skip to content

Always use HTTPS for the Data API - #2

Merged
taplin merged 1 commit into
mainfrom
https-only
Oct 26, 2026
Merged

taplin merged 1 commit into
mainfrom
https-only

Conversation

@taplin

@taplin taplin commented Oct 26, 2026

Copy link
Copy Markdown
Collaborator

Found while drafting the 1.0.0 release notes. For any port other than 443, FileMakerServer and FMPSession built http:// URLs. On a server reached at, say, port: 8443, the login request sent its Authorization: Basic header in cleartext, and every later request sent the bearer token the same way.

FileMaker Server serves the Data API only over HTTPS, so the port-based scheme switch had no legitimate use. All four URL builders (database list, login, logout, baseURL) now always use https://.

Test: the new Transport suite records the URLs a FileMakerServer actually requests through a stub URLProtocol, on ports 443, 8443 and 80, for one unauthenticated call and one call that logs in. Every URL has to be https on the configured port. The suite fails on the old code (ports 8443 and 80) and passes now.

Verified: 17 tests pass on macOS (Xcode, warnings as errors) and on Linux with Swift 6.2 and 6.4 (swift:*-noble, warnings as errors).

I'm holding the DataAPI 1.0.0 tag until this merges, so 1.0.0 doesn't ship with the cleartext path. AdminAPI already uses HTTPS only, and AuthNet's endpoints are fixed HTTPS URLs.

🤖 Generated with Claude Code

Requests to any port other than 443 went out over plain HTTP, including the login request carrying Basic credentials. FileMaker Server serves the Data API only over HTTPS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@taplin
taplin merged commit 4eee107 into main Oct 26, 2026
16 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.

1 participant