Request to Cancel v2 Redirection for Icons When Using Non-Standard Ports

[chenjuefei]

Since updating to version v0.21.0, while using a non-standard port for reverse proxying, all icon links are automatically, resulting in a 302 redirect. This change has disrupted the normal display and functionality of icons. I kindly request reconsideration of this redirection behavior, as it complicates configuration without clear benefits. Feedback on this matter would be greatly appreciated.

[Frooodle]

non-standard port can you define what you mean by this?

[chenjuefei]

I apologize for the lack of clarity in my initial description. I'm using Nginx Proxy Manager (NPM) to reverse proxy Stirling-PDF. Due to network configurations, the service port on NPM is set to non-standard ports instead of the typical 80 or 443. For example, accessing https://example.com:2443/site.webmanifest?v=2 results in a 302 redirect to https://example.com/site.webmanifest. I've tried modifying the settings in NPM with proxy_set_header Host $host:2443, but this introduces other issues like mixed content errors. All these problems began with the update to version v0.21.0; everything was working fine before then.