How to hide #document (Public URL) in browser source code that has already been encrypted?

Anonymous
2024-03-04T02:48:50+00:00

The public URL of the powerbi report was already encrypted so that it does not appear in the browser's source code, but it began to appear in the #document tag recently, this tag is created automatically once the system made in angular, node v16.13.1 is published.

The URL encryption was made so that it would not be displayed in the browser's source code, but recently it started appearing that way in #document. The tests carried out have not been successful in hiding this label.

Windows for business Windows Server Devices and deployment Set up, install, or upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-04T03:40:24+00:00

    Hi Marco López CR,

    unfortunately, I am not able to provide support for third-party applications or custom code. However, I suggest reaching out to the support team of the application or developer who created the code for further assistance. They may be able to provide more specific guidance on how to resolve this issue.

    Have a nice day.

    Kind regards,

    Lei

    0 comments No comments
  2. Anonymous
    2024-03-05T15:09:45+00:00

    I am the developer of the web system. A development was already applied to encrypt the URL of the public Powerbi report, but it began to appear in this #document(url) tag within the iframe.

    0 comments No comments
  3. Anonymous
    2024-03-06T01:47:15+00:00

    I'm sorry.

    Since there are no engineers dedicated to Web development in this forum. You will need to repost your question in the forum for Web development, where there will be a dedicated engineer to provide you with a professional and effective response.

    0 comments No comments