Fixed issue in path matching middleware

ulrack · Jan 17, 2021 · f9955ee · f9955ee
1 parent c38284c
commit f9955ee
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 - Fixed issue where it was possible to get more output after a 404 was generated.
+- Fixed issue path and route were not equally treated in path matching middleware.
 
 ## 3.0.0 - 2021-01-17
 
@@ -42,7 +43,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - The initial implementation of the package.
 
 # Versions
-- [3.0.1 > Unreleased](https://github.com/ulrack/web/compare/3.0.0...HEAD)
+- [3.0.1 > Unreleased](https://github.com/ulrack/web/compare/3.0.1...HEAD)
 - [3.0.0 > 3.0.1](https://github.com/ulrack/web/compare/3.0.0...3.0.1)
 - [2.0.0 > 3.0.0](https://github.com/ulrack/web/compare/2.0.0...3.0.0)
 - [1.0.1 > 2.0.0](https://github.com/ulrack/web/compare/1.0.1...2.0.0)

diff --git a/src/Component/Middleware/PathMatchingMiddleware.php b/src/Component/Middleware/PathMatchingMiddleware.php
@@ -81,6 +81,7 @@ private function getParameters(
         string $path
     ): ?array {
         $route = trim($route, '/');
+        $path = trim($path, '/');
 
         $matchParam = preg_match(
             '/{[^\/]+}/',