Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All redirects rules not working #214

Open
MrMarcusAndersson opened this issue Apr 20, 2021 · 1 comment
Open

All redirects rules not working #214

MrMarcusAndersson opened this issue Apr 20, 2021 · 1 comment

Comments

@MrMarcusAndersson
Copy link

We are using version 11.3.

The issue occurs in the production environment, but not in development.

We are experiencing issues where some redirects work and some don't. Sometimes an added redirect work when we add it, but after a restart of the site the same redirect won't work.

There are about 2000 redirect rules. The first 300+ work, but most of the latter 1700 redirects don't work.

We see alot of rows in the log like these:
2021-04-20 10:23:29,048 DEBUG [] BVNetwork.NotFound.Core.RequestHandler - Not handled. Current URL is ignored or no redirect found. Request URL: _http://www.website.com/whateverpage_ Response status code: 404 [10:30 AM] 2021-04-20 10:22:01,107 DEBUG [] BVNetwork.NotFound.Core.RequestHandler - Skipping request with 404; in the query string. Request URL: _http://www.website.com/notfound?404;http://www.website.com:80/whateverpage2_ Response status code: 404

The website uses SSL and is accessed via https, but the certificate and redirect is not happening on the IIS but rater in Bigip by the hosting.

We can see all redirect rules in Episerver Dashboard and also in the database table.

We are at a loss and any help is greatly appreciated.

@marisks
Copy link
Member

marisks commented Apr 20, 2021

It is quite hard to understand what is happening from your description.
Version 11.3 is already using SQL Server as storage and has no limitation on how many redirects are loaded from the database.
Regarding the logged "404;" - as I remember it means that the URL was handled already handled by another handler (IIS or ASP.NET) and the 404 handler will not try to handle those again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants