Legacy Knowledge Base
Published Sep. 10, 2025

java.net error URISyntaxException:Illegal character in path at index 0 occurred during the export process

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 exporting web content, users keep running into errors, but the export is still successful despite the number of errors.
  • Steps to reproduce:
    1) Startup DXP 7.3 u23
    2) Create a structure with 'text', 'image', and 'Link to page' fields
    3) Create web content from this structure and one basic web content
    4) Navigate to publication> Export and try to export
    Expected Behavior: The export process is successful.
    Observed Behavior: The export process is successful with the following errors 

    ERROR [liferay/background_task-4][HttpComponentsUtil:390] null
    com.liferay.portal.kernel.log.LogSanitizerException: java.net.URISyntaxException: Illegal character in path at index 0: <?xml version="1.0"?>__<root available-locales="en_US"default-locale="en_US" version="1.0">_       <dynamic-element index-type="" instance-id="EEyvJHNl" name="FieldsGroup58466005" type="fieldset">_              <dynamic-element index-type="keyword" instance-id="sV5xg7Z4" name="Text79630757" type="text">_                      <dynamic-content language-id="en_US"><![CDATA[Web Content 3]]></dynamic-content>_           </dynamic-element>_             <dynamic-element index-type="keyword" instance-id="Owl5PNmh" name="Upload42878555" type="document_library">_
                    <dynamic-content language-id="en_US"><![CDATA[{"classPK":43000,"groupId":"20123","title":"Asset2.jpg","type":"document","uuid":"bcf76f36-8a35-0278-e7fb-152b1930c169"}]]></dynamic-content>_                </dynamic-element>_             <dynamic-element index-type="keyword" instance-id="0825klPD" name="Numeric40046757" type="numeric">_                        <dynamic-content language-id="en_US"><![CDATA[9999999999]]></dynamic-content>_          </dynamic-element>_             <dynamic-element index-type="keyword" instance-id="NaxVSjAw" name="LinkToPage94792237" type="link_to_layout">_                      <dynamic-content language-id="en_US"><![CDATA[{"groupId":20123,"id":"e59a41e7-e366-73fd-c1b7-f825def8ef8a","layoutId":"2","name":"Pages > Home","privateLayout":false,"value":"\/home"}]]></dynamic-content>_               </dynamic-element>_ </dynamic-element>_</root> [Sanitized]
            at java.net.URI$Parser.fail(URI.java:2848) ~[?:1.8.0_201]
            at java.net.URI$Parser.checkChars(URI.java:3021) ~[?:1.8.0_201]
            at java.net.URI$Parser.parseHierarchical(URI.java:3105) ~[?:1.8.0_201]
            at java.net.URI$Parser.parse(URI.java:3063) ~[?:1.8.0_201]
            at java.net.URI.<init>(URI.java:588) ~[?:1.8.0_201]
            at com.liferay.portal.kernel.util.HttpComponentsUtil.getURI(HttpComponentsUtil.java:455) ~[portal-kernel.jar:?]
            at com.liferay.portal.kernel.util.HttpComponentsUtil.getProtocol(HttpComponentsUtil.java:387) [portal-kernel.jar:?]
            at com.liferay.portal.kernel.util.HttpComponentsUtil.hasProtocol(HttpComponentsUtil.java:476) [portal-kernel.jar:?]

     

Environment

  • Liferay DXP 7.4 update 23

Resolution

  • The observed errors are the result of a known bug that was addressed in DXP 7.4 update 26.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base