You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
url parsing fails if front slash before fragment is missing and no path specified #131
That is correct: https://portal.azure.com#@930d042 (fragment following an empty path) is a valid URI.
We rely on go stdlib url.ParseRequestURI() to validate. And that one is confused by this construct.
Activity
fredbi commentedon Mar 14, 2025
That is correct: https://portal.azure.com#@930d042 (fragment following an empty path) is a valid URI.
We rely on go stdlib url.ParseRequestURI() to validate. And that one is confused by this construct.
https://portal.azure.com/#@930d042f-8145 -> with a slash following the hostname is less prone to errors.²
repro go-openapi#131
repro go-openapi#131
repro go-openapi#131
repro go-openapi#131
fix: validate "uri" format for absolute URIs with a fragment (go-open…
fix: validate "uri" format for absolute URIs with a fragment (go-open…
fix: validate "uri" format for absolute URIs with a fragment (#131) (#…
repro go-openapi#131