Share via

Web application proxy

Suleman Fasasi 0 Reputation points
2025-12-11T13:34:29.3133333+00:00

When downloading DOCX files that have names containing Polish special characters, the download completes successfully, but the file is saved with the name Download.aspx. However, once it is renamed, it becomes a normal DOCX file.

On the internal network, everything works without any issues. This situation only occurs when we are outside the network and the traffic passes through the AWAP. You can check an example using the following link: [Download with Polish special characters]: (https://www.ourjm.com/Portal/Url.aspx?id=2aed8211-5853-4f0f-80c3-c614a524dc67)

Interestingly, if we upload the same file but without Polish special characters, the issue does not occur and everything works correctly. This case can be verified using the following link: [Download without Polish special characters] (https://www.ourjm.com/Portal/Url.aspx?id=d99f29d6-7c25-41d7-ae44-d9816cbed9ae)

Azure Web PubSub
Azure Web PubSub
An Azure service that provides real-time messaging for web applications using WebSockets and the publish-subscribe pattern.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-11T13:34:39.5033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you're experiencing with downloading DOCX files that have Polish special characters in their names appears to be related to how the Azure Web Application Proxy (AWAP) handles file downloads with special characters. When the file is downloaded, it is being saved as Download.aspx instead of retaining the original file name, which suggests that the proxy may not be correctly handling the character encoding or the content disposition header for files with special characters.

    This behavior is not observed on the internal network, indicating that it is specific to the external access through the AWAP. It is common for proxies to have issues with special characters in URLs or file names, which can lead to unexpected results like the one you are seeing.

    One potential workaround is to ensure that the application serving the files correctly sets the Content-Disposition header to specify the filename, which can help browsers understand how to save the file. Additionally, you may want to check if there are any specific configurations or updates available for the AWAP that address handling special characters in file names.

    If the issue persists, consider reaching out to Microsoft support for further assistance with the Azure Web Application Proxy configuration and its handling of special characters in file downloads.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.