New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request to Cancel v2 Redirection for Icons When Using Non-Standard Ports #1113
Comments
|
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 |
After updating to version 0.24.3, I encountered even more issues than expected. I discovered that a large number of CSS and JS files could be subject to 302 redirects. I had no choice but to diligently search for a solution. Finally, I found the following method, and I hope it won't cause any additional problems.
|
I have the same problem. Due to v2 redirections I get 302 and 502 errors for all files that use “?v=2". So, my Stirling-PDF installation is only partly useable because part of the UI is broken. |
Awesome. Version 0.24.5 solved this issue! |
Thank's for the new version. The proxy works and the UI looks great now! |
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.
The text was updated successfully, but these errors were encountered: