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

Separation of concerns: grammar for URL components instead of whole URLs #377

Open
ralfhandl opened this issue Mar 20, 2024 · 0 comments
Open

Comments

@ralfhandl
Copy link
Contributor

ralfhandl commented Mar 20, 2024

We have published ABNF rules for OData request URLs

  • odataUri
  • odataRelativeUri
  • resourcePath
  • queryOptions

which are much complicated by the fact that they are defined for percent-encoded URLs. Because of ODATA-1583, much of these rules must be duplicated for the context rule, which (being a URL fragment) needs different percent-encoding.

It would be much easier if we assume that the "raw" URL has already been split and percent-decoded in compliance with the WHATWG URL Standard and provide grammars for the components of a URL:

  • path
  • search parameter name
  • search parameter value
  • fragment

Consider writing an alternative set of grammars with this approach.

Imported from ODATA-1606

@HeikoTheissen HeikoTheissen modified the milestone: 4.02 Mar 22, 2024
@ralfhandl ralfhandl changed the title Separation of concerns: ABNF for URL components instead of whole URLs Separation of concerns: grammar for URL components instead of whole URLs Mar 27, 2024
@ralfhandl ralfhandl moved this to Open in OData TC Apr 24, 2024
@ralfhandl ralfhandl removed the status in OData TC Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants