Bug #89641
closedRouting configuration with 3rd party url segments
0%
Description
An extension configures a speaking url segement as following:
routeEnhancers: JobvacPlugin: type: Extbase limitToPages: - 119 extension: Jobvac plugin: Joblist routes: - routePath: '/{job_title}' _controller: 'Job::show' _arguments: job_title: job defaultController: 'Jobvac:joblist' aspects: job_title: type: PersistedAliasMapper tableName: tx_jobvac_domain_model_job routeFieldName: slug
In the global configurations the following is present:
[FE][cacheHash][excludedParameters] = L,pk_campaign,pk_kwd,utm_source,...
Calling the url
...{page}/{slug}
works fine where calling
...{page}/{slug}?utm_source=test
causes a runtime exception:
(1/1) #1544172838 RuntimeException Error handler could not fetch error page "/pages/startpage", reason: Couldn't get URL: /pages/startpage
Without the routing configuration it works fine.
Updated by Susanne Moog almost 5 years ago
- Sprint Focus set to On Location Sprint
Updated by Oliver Hader almost 5 years ago
Side note: exception 1544172838
is caused by internal page request for errorHandling
Updated by Oliver Hader almost 5 years ago
- Status changed from New to Needs Feedback
- Tags set to pending-close
- Sprint Focus deleted (
On Location Sprint)
cHash handling probably has been fixed with issue #86895 on Git 9.5
branch (I could not reproduce with and without that change using your ?utm_source=abc
example being configured in excluded parameters as mentioned)
Error message Couldn't get URL: /pages/startpage
stems from sending an internal HTTP request to resolve 404 page. Could you please try to temporary disable 404 error handling just to check whether there's still a misbehavior in route resolving and cHash or whether it is related to error handling? Thanks in advance for your feedback!
Updated by Oliver Hader almost 5 years ago
- Related to Bug #86895: routeEnhancer not working correct for paginate widget added
Updated by Oliver Hader about 4 years ago
- Status changed from Needs Feedback to Closed
Seems to be fixed, closing issue.