[MAGNOLIA-274] recursive redirect when changing name of feature page to something else Created: 02/Feb/05  Updated: 03/Feb/05  Resolved: 03/Feb/05

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.0 Final
Fix Version/s: 2.01

Type: Bug Priority: Minor
Reporter: edd spreeuwers Assignee: Boris Kraft
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

I started using Magnolia as a CMS for a primary school running on a machine with win2000. (nice GUI for non tech users)


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Altering the name of the features page in for example start
publishing this and then retrieving the deafultpage:
http://localhost:8082/ will result in recursive redirecting of the page
resulting in a continues reload of the page..
In firefox is results in an errormessage for a redirect..

If you exactly type the URL http://localhost:8082/start.html this will not occur



 Comments   
Comment by Boris Kraft [ 03/Feb/05 ]

This works as designed. The default page if a resource is not available is defined as features.html. If that is not there, it results in the mentioned redirect loop. To change that, set Config: /server/ResourceNotAvailableURIMapping to a different page.

Generated at Mon Feb 12 03:15:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.