[MBLINKS-11] Default settings of linkmapper service creates infinite loop in our cloud infrastructure Created: 31/Jan/18  Updated: 23/Feb/18  Resolved: 01/Feb/18

Status: Closed
Project: Link Mapper
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0, 1.0.6

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

To Reproduce:

– On a cloud instance, open a page that does not exist : https://public-uat-magnolia-docs.staging.magnolia-now.com/invalidpage (might not work anymore)
– Instead of getting a 404, request timeouts and returns a 504 after a few seconds

Analysis

The logs show that linkmapper tries to call a service located at this address http://localhost:8080/v1/lima for all 404. Unfortunately this points to magnolia itself which will treat it as another 404 and will loop.

This setting is bootstraped by the module by default


Generated at Mon Feb 12 02:22:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.