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

Exclude URL encode sets from extension command name #566

Closed
andreastt opened this issue Jan 18, 2017 · 0 comments
Closed

Exclude URL encode sets from extension command name #566

andreastt opened this issue Jan 18, 2017 · 0 comments
Labels
Milestone

Comments

@andreastt
Copy link
Member

We ought to exclude the default encode set and the user encode set (which is a superset of the former) from our definition of what characters extension command paths can contain.

(Follow-up from #551 (comment).)

@andreastt andreastt added the bug label Jan 18, 2017
@andreastt andreastt added this to the Level 1 milestone Jan 18, 2017
@andreastt andreastt changed the title Exclude URL encode sets from extension command prefix Exclude URL encode sets from extension command URL Jan 18, 2017
@andreastt andreastt changed the title Exclude URL encode sets from extension command URL Exclude URL encode sets from extension command name Jan 18, 2017
AutomatedTester pushed a commit that referenced this issue Jan 18, 2017
This effectively excludes the default- and user encode sets which
contains unwanted characters to include in the concatenated URL that
makes up the extension command URL.

Fixes: #566
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant