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

Consider supporting prefix wildcard characters in WAOA "paths" field #30

Open
prarthana-s opened this issue Aug 19, 2021 · 1 comment
Open

Comments

@prarthana-s
Copy link

The web-app-origin-association file's "paths" field currently only supports wildcard characters at the end of the path. For example:

"paths":["/"]
"paths":["/documents/
"]

However, if I specify a path such as ["*/news"], this is unsupported as the wildcard character is not at the end of the path.

Can you please consider supporting wildcard characters at the beginning of paths too? This will be useful for applications whose paths may be dynamic with data such as an identifier/username/location but have a common suffix path. For example, "/usa/news" and "/uk/news", which can be specified as ["*/news"].

@LuHuangMSFT
Copy link
Collaborator

I think this is a good idea that will not negatively impact performance (both prefixes and suffixes are easy to match). Developers should have more flexibility in syntax to define the set of paths to include or exclude.
I'll open a PR shortly to address this.

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