You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
Umbraco v9 RC4
Bug summary
Accessing a URL in Umbraco that gets handled by a content finder, the content finder successfully triggers and calls request.SetRedirect(url) and returns true, but the site is getting redirected to /account/accessdenied in some kind of infinite loop until the error The request filtering module is configured to deny a request where the query string is too long. is thrown.
Specifics
No response
Steps to reproduce
Create a content finder that redirects to a parent node
Register the content finder before ContentFinderByUrl
Call a URL on the front end that gets handled by the content finder
Response ends up in an infinite loop
Expected result / actual result
I'd expect to be redirected accordingly to the returned URL.
The text was updated successfully, but these errors were encountered:
* Fixes#11189
* Fixes#11183
* Fix test Null_When_No_Content_On_PublishedRequest.
Believe this is reasonable.
* Update src/Umbraco.Web.Website/Routing/PublicAccessRequestHandler.cs
Co-authored-by: Paul Johnson <[email protected]>
Co-authored-by: Bjarke Berg <[email protected]>
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
Umbraco v9 RC4
Bug summary
Accessing a URL in Umbraco that gets handled by a content finder, the content finder successfully triggers and calls
request.SetRedirect(url)
and returnstrue
, but the site is getting redirected to/account/accessdenied
in some kind of infinite loop until the errorThe request filtering module is configured to deny a request where the query string is too long.
is thrown.Specifics
No response
Steps to reproduce
ContentFinderByUrl
Expected result / actual result
I'd expect to be redirected accordingly to the returned URL.
The text was updated successfully, but these errors were encountered: