[MULTISITE-186] Multisite DomainNamePathTransformer creates incorrect external Links Created: 10/Jan/24  Updated: 16/Jan/24  Resolved: 11/Jan/24

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.0, 2.1.4

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MULTISITE-180 Default port is added for https links Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Epic Link: Support
Team: DeveloperX
Work Started:
Approved:
Yes

 Description   

Steps to reproduce

  1. Create a site definition that doesn't define port in domain
  2. Define protocol to https
  3. Generate a link with LinkUtil.createExternalLink(node)

Expected results

The link gets generated as in 6.2.40, without a set port

Actual results

The link gets the 80 port appended regardless of the protocol being used.

Development notes

This was caused by the changes onĀ MULTISITE-180


Generated at Mon Feb 12 06:07:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.