Legacy Knowledge Base
Published Jun. 30, 2025

Image URLs in headless API responses include the port number

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

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 URLhttps://localhost:8080/o/commerce-media/accounts/-9223372036854775808/attachments/47489?download=true
    Relative URLo/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
Did this article resolve your issue ?

Legacy Knowledge Base