Issue
- While using the headless API, users can see the port with the source URL.
Environment
- Liferay DXP 7.4
- Commerce 4.0
Resolution
- This is the expected behavior as Liferay is either serving the full URL, including the port number, or just the relative URL. For example:
Full URL:https://localhost:8080/o/commerce-media/accounts/-9223372036854775808/attachments/47489?download=true
Relative URL:o/commerce-media/accounts/-9223372036854775808/attachments/47489?download=true
In regard to commerce, the port number is part of the standard Liferay pattern for the full URL, so this is not something that is going to change here.
Additional Information
- Users can customize the URL value received and remove the port number before serving it to non-admin and non-logged-in users if they have such requirements.
- A relative URL is one that just contains the path. The path includes everything after the domain, including the directory and slug. Since relative URLs do not provide the whole URL structure, it is assumed that when linking a relative URL, it uses the same protocol, subdomain, and domain as the page it is on. A relative URL is useful within a site to move a user from one location to another within the same domain.
- How to modify API URL
Subscriber Exclusive Content
A Liferay Enterprise Subscription provides access to over 1,500 articles that include best practices, troubleshooting, and other valuable solutions. Sign in for full access.
Sign In