".." in URL path resolves correctly, "//" does not

[sblive]

rules like
@app.route("/api/v1/system/status", methods=["GET"])
get correctly matched by e.g.
/api/v1/system/status/../status
/api/v1/system/blahblahdoesnotexist/../status
but not by
/api/v1/system//status
/api/v1/system///status

I did not test if the recent fix of #207 caused this

[miguelgrinberg]

I'm confused. None of the examples that you have showed above match the example route that you are using, and that is actually correct. Your route doesn't have any dynamic segments, so only the same exact URL will match. This is true before and after the change I've made yesterday.

>>> p = URLPattern('/api/v1/system/status')
>>> p.match('/api/v1/system/status/../status') is not None
False
>>> p.match('/api/v1/system/blahblahdoesnotexist/../status') is not None
False
>>> p.match('/api/v1/system//status') is not None
False
>>> p.match('/api/v1/system///status')  is not None
False
>>> p.match('/api/v1/system/status') is not None
True

[sblive]

that's weird, I just retested and still this works:
/api/v1/system/asdf/../status
which I believe to be correct and all (?) webservers support.
for multi slashes (which most webservers support) the easy fix would be to replace all multiple slashes in path with single slash.
maybe you don't think it's a bug, I guess it's an interpretation thing and not that important ;)

[miguelgrinberg]

@sblive How are you testing this exactly?

[sblive]

I'm sorry, you are right. it seems wget (which I used) and browsers already translate this, so I realized that microdot will never see those URLs. sorry for the confusion!