Unable to put consecutive slashes in route path about mockoon

[mivanov]

Forgot to mention, I love Mockoon, thank you for this glorious thing!

[255kb]

so what about:

1. define a route /test/xxxx
2. request it with /test////xxxx
3. app convert it to /test/xxxx so you get the declared route with defined status without any redirection?

[255kb]

ok, it's done, it will be released in v1.0.0 in the coming weeks (before end of August), thanks for your help 👍

[255kb]

Thanks, I love that you love Mockoon 😄

Concerning the // I will rewrite the url to match the input mask that remove consecutive slashes.
What do you think, should I silently serve the route (the URL still shows multiple slashes) or redirect with a 301?

[mivanov]

I have seen all variations, since it's up to the server or sometimes application, but I believe silently serving the route is most common. In my experience I would rank them like this in order from most common to least common:

1. 200
2. 302
3. 404
4. 301 maybe, but I'm honestly not sure I have seen this.

I would be happy with a 200, or with allowing consecutive slashes so one could replicate any behavior.

[mivanov]

That makes perfect sense and would solve the issue I had.