Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WAFastCGIRequestConverter>>#requestUrlFor: signals a WAInvalidUrlSyntaxError when the ‘REQUEST_URI’ is ‘/?://’ #1376

Closed
Rinzwind opened this issue Sep 6, 2023 · 0 comments

Comments

@Rinzwind
Copy link
Member

Rinzwind commented Sep 6, 2023

When the ‘REQUEST_URI’ parameter is /?:// in WAFastCGIRequestConverter>>#requestUrlFor:, a WAInvalidUrlSyntaxError is signaled, although /?:// is a valid ‘origin-form’ per section 3.2.1 in RFC 9112.

The relevant rules from RFC 9112, RFC 9110 and RFC 3986 are:

origin-form   = absolute-path [ "?" query ]

absolute-path = 1*( "/" segment )

segment       = *pchar

query         = *( pchar / "/" / "?" )

pchar         = unreserved / pct-encoded / sub-delims / ":" / "@"
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

No branches or pull requests

2 participants