The Wayback Machine - https://web.archive.org/web/20200611001731/https://github.com/julienschmidt/httprouter/issues/114
Skip to content

/ httprouter

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

Jump to bottom

clarify status of non-full-segment parameters #114

Open
rogpeppe opened this issue Nov 16, 2015 · 1 comment
Open

clarify status of non-full-segment parameters #114

rogpeppe opened this issue Nov 16, 2015 · 1 comment
Labels
bug
Projects
v2
Milestone
v2

Comments

@rogpeppe
Copy link
Contributor

@rogpeppe rogpeppe commented Nov 16, 2015

The documentation does not make it clear whether
paths of the form:

/prefix:foo

are allowed. These are currently supported by httprouter,
but don't seem quite in the spirit of its simple specification
(you can't have statically defined suffixes for a path element,
so why should you be allowed a statically defined prefix?)

This form:

/prefix*foo

is similarly not specified but is explicitly disallowed. The two forms should
perhaps be made consistent with each other.
@julienschmidt julienschmidt added the bug label Dec 2, 2015
@julienschmidt julienschmidt added this to the v2 milestone Dec 2, 2015
@mpnally
Copy link

@mpnally mpnally commented Mar 16, 2016

Please don't fix this by disallowing /prefix:foo; I am using that capability
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug
3 participants
@rogpeppe @julienschmidt @mpnally
You can’t perform that action at this time.