OpenAPI paths containing colons create invalid Windows filenames
A valid route such as /stuff:action could not be generated on Windows because colons are forbidden in filenames.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1381
- Reporter
- xehmer
- Reported
- September 2, 2025
- Reported version
- 1.4.2
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2025
- Classification confidence
- High
- Chronology confidence
- Medium
- Accepted correction
- PR #1386
- First fixed release
- 1.4.5
- Report to release
- 2.61 elapsed daysReport: 2025-09-02T09:46:13Z; corrected publication: 2025-09-05T00:17:55.340Z.
Finding
The filename scheme is confirmed affected years before the report. The precise earliest affected package is bounded rather than asserted beyond the available tagged comparison.
Evidence trail
Origin
Confirmed affected by: 7cd98d5a, committed October 3, 2022; confirmed affected release 0.10.3. Route-to-file generation used URL path text as filename text without a Windows-safe transformation.
Source history and behavioral evidence
The long-standing route filename scheme retained the colon. The fix introduces one Windows-safe transformation and adds a colon-bearing OpenAPI route to black-box and generator coverage.
Release chronology
The behavior is confirmed by 0.10.3 and in the reported 1.4.2. The fix shipped in 1.4.5 three calendar days after the report.