Behavior change in 1.3.2 with double slashes when RedirectFixedPath is false

[fasthttp]

Behavior change in 1.3.2 with double slashes when RedirectFixedPath is false

[savsgio]

Hi @oschwald,

This is an old bug, and now has the correct behaviour, because to response a 200 status code, the requested url path must be equal to the registered path in the router.

Sorry!

[savsgio]

For that, the RedirectFixedPath flag try to correct the "incorrect" path with a redirection

[oschwald]

Ah, if this change was intentional, it would have been nice to specifically mention it in the change log and to at least do a minor version bump instead of a patch version bump. We unfortunately had clients depending on the behavior and had to revert.

[savsgio]

Hi @oschwald,

I've just been updated the release notice in the release about the possible break in the path.

I'm really sorry, but the fix is ​​needed. I have treated it as a fixed version and not as a minor version because it is a bugfix, not a new feature.