Routing
exception
Matched route
Route Parameters
No parameters.
Route Matching Logs
Path to match:
/exception
# | Route name | Path | Log |
---|---|---|---|
1 | _preview_error | /_error/{code}.{_format} | Path does not match |
2 | _wdt | /_wdt/{token} | Path does not match |
3 | _profiler_home | /_profiler/ | Path does not match |
4 | _profiler_search | /_profiler/search | Path does not match |
5 | _profiler_search_bar | /_profiler/search_bar | Path does not match |
6 | _profiler_phpinfo | /_profiler/phpinfo | Path does not match |
7 | _profiler_search_results | /_profiler/{token}/search/results | Path does not match |
8 | _profiler_open_file | /_profiler/open | Path does not match |
9 | _profiler | /_profiler/{token} | Path does not match |
10 | _profiler_router | /_profiler/{token}/router | Path does not match |
11 | _profiler_exception | /_profiler/{token}/exception | Path does not match |
12 | _profiler_exception_css | /_profiler/{token}/exception.css | Path does not match |
13 | access_risk_add | /access-risk/add | Path does not match |
14 | app_alert_sendemail | Path does not match | |
15 | app_alert_rrm | /rrm-action | Path does not match |
16 | registre_alerts2 | /api-core/alertsx | Path does not match |
17 | registre_alerts | /api-core/alerts/{year} | Path does not match |
18 | registre_alertsv2 | /api-core/alertsv2/{year} | Path does not match |
19 | cluster_childs | /list/subcluster/{id} | Path does not match |
20 | sub_cluster | /list/activity/{id} | Path does not match |
21 | indicator | /list/indicator/{id} | Path does not match |
22 | typeactivitywash | /list/typeactivitywash/{atw} | Path does not match |
23 | subActivity | /list/subActivity/{id} | Path does not match |
24 | contact | /contact | Path does not match |
25 | app_drc | /cd | Path does not match |
26 | app_cf | /cf | Path does not match |
27 | app_bur | /bf | Path does not match |
28 | crisis_register_zone_intervention | /crisis_register_zone_intervention | Path does not match |
29 | exception | /exception | Route matches! |
Note: These matching logs are based on the current router configuration, which might differ from the configuration used when profiling this request.