Access string matched against wildcard

[untitaker]

The Python webframework Flask has the following syntax for routing expressions:

/foo/<var1>/bar/  # var1 is a string

/foo/var2:int/bar/ # var2 is matched iff it is parseable as int
/foo/var3:customtype/bar/ # var3 is matched against a custom type that has to be registered upfront

The whole typesystem is a thing I'd like to see in the Iron router middleware, but I'm primarily interested in the following:

/foo/<var4:path>/bar/

That route will match against:

• /foo/baz/bar/, var4="baz"
• /foo/baz/bam/bar/, var4="baz/bam"

and so on. I know that I can match against wildcards, but I need a way to access the matched path segments.

[leoyvens]

Router relies on route-recognizer to do the heavy url parsing, the patterns router supports are the same route-recognizer supports. You can open an issue there, but tbh it hasn't been updated in a while.

[reem]

It's possible we should move to our own parser, but honestly I just don't have the time to write one right now.

[SlNPacifist]

Router lets you access wildcard fields. Documentation is not clear about it, but current syntax is: /foo/*var4/bar/. The only real difference between /foo/:var4/bar/ and /foo/*var4/bar/ is that : does not allow you to have / in var4 while * allows. So try /foo/*var4/bar/ route and you will find that it matches /foo/baz/bam/bar/ having var4=baz/bam

[untitaker]

Hello @SlNPacifist, thanks for your response. I guess that basically closes this issue.

However, I have one issue left: When I do /storage/:userid/*path, path never contains a trailing slash, regardless how the request is sent. In my case it is very important to have this distinction.

[leoyvens]

@untitaker that looks more like an actual bug in route-recognizer, worth an issue. Maybe using two routes, one with a trailing slash, would be a workaround.

[untitaker]

@leodasvacas I've published a testcase at http-rs/route-recognizer#17, it doesn't seem to fail. Not sure what else could be at fault. request.url.path does show a difference between the two URLs.

[leoyvens]

@untitaker Thanks for investigating, not sure what's happening. In an older version of router we used to strip trailing slashes, but the latest release differentiates "/foo" from "/foo/".

[untitaker]

Actually I'm hitting #82, I think.

[untitaker]

Nevermind, it was some unrelated bug in my system.