Routing
client_legal_page
Matched route
Route Parameters
No parameters.
Route Matching Logs
Path to match:
/legal
| # | Route name | Path | Log |
|---|---|---|---|
| 1 | app_login | /login | Path does not match |
| 2 | app_logout | /logout | Path does not match |
| 3 | category_search | /api/category/search | Path does not match |
| 4 | content_search | /api/content/search | Path does not match |
| 5 | content_search_by_type | /api/content/search/by_type | Path does not match |
| 6 | content_preview | /content-preview | Path does not match |
| 7 | content_get_by_sector | /api/content/get-by-sector | Path does not match |
| 8 | content_get_by_subsector | /api/content/get-by-subsector | Path does not match |
| 9 | api_get_similar_jobs | /api/job/get-similar-jobs | Path does not match |
| 10 | manage_content_request | /admin/contentrequest/{id}/manage | Path does not match |
| 11 | client_contact_page | /contact | Path does not match |
| 12 | client_press_page | /press | Path does not match |
| 13 | client_legal_page | /legal | Route matches! |
Note: These matching logs are based on the current router configuration, which might differ from the configuration used when profiling this request.