Developer forum

Forum » Dynamicweb 10 » Bug in R1 Release Ring - Unauthorized Page Access Returns 404 Instead of Redirecting to Sign-in

Bug in R1 Release Ring - Unauthorized Page Access Returns 404 Instead of Redirecting to Sign-in

Pedro Meias
Reply

Hi,

Reporting a bug in R1 release ring where not logged in users where not being redirected to sign-in page.

This was fixed by moving the site back to R2.

In R1 version.

Home page as the following permissions

When accessing the Home page. We get a 404.

After moving the site to R2. with the same settings we are now redirect to sign-in page

Thank you.


Replies

 
Oleg Rodionov Dynamicweb Employee
Oleg Rodionov
Reply

Hi,

I've tried to reproduce the issue on Swift 2 test solution based on last R1 (10.21.6) but was not abled to catch it, signin page apppears as expected (find attachment for details). Try to recycle IIS pool of your solution first of all. 

Oleg QA 

Screenshot_2025-12-05_093232.png Screenshot_2025-12-05_093426.png Screenshot_2025-12-05_093511.png
 
Pedro Meias
Reply

Hi Oleg,

Even after recycling IIS pool the issue persists. I have attached a zip file with 2 videos of the solution in R1 and R2.

If there is anything else I can provide. Let me know.

Thank you for your help.

 
Oleg Rodionov Dynamicweb Employee
Oleg Rodionov
Reply

Hi Pedro,

thanks for the details. Your case seems to be based on Swift 1 template set uses old extranet login module and appropriate navigation tag to redirect to sign in page. It's know bug, scope of task #26575 already fixed and merged to R1 on last Friday but not yet shared to download , I hope it will be provided in next ring release soon. Sorry for inconvinience.

BR, Oleg QA

 

You must be logged in to post in the forum