We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
/?://
WAFastCGIRequestConverter>>#requestUrlFor:
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 / ":" / "@"
The text was updated successfully, but these errors were encountered:
Fixed #initializeFromString: in WAUrl to take into account that ‘://’…
da095f6
… can also be included in the query (see: SeasideSt#1376).
No branches or pull requests
When the ‘REQUEST_URI’ parameter is
/?://
inWAFastCGIRequestConverter>>#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:
The text was updated successfully, but these errors were encountered: