When using custom ports (e.g. 5200, 6000, 10000 ...etc.).
The application works fine for all URL directions except during the following actions:
- Login: After filling the credentials and clicking on "Login" button
- Logout: After clicking on the "Logout" button
Then, the application redirect the user to a URL without keeping the custom port, and by default it will go to the default port (443 in HTTPS, and 80 in HTTP).
And the user will need to re-enter the port number again and refresh the page in order for them to access the system.
The issue was experienced in the Dockerized image with Nginx proxy server, I did not try it on the direct JAR installation.
Versions where the issue was experienced 7.45 and 7.46. I did not try it on different versions.
When using custom ports (e.g. 5200, 6000, 10000 ...etc.).
The application works fine for all URL directions except during the following actions:
Then, the application redirect the user to a URL without keeping the custom port, and by default it will go to the default port (443 in HTTPS, and 80 in HTTP).
And the user will need to re-enter the port number again and refresh the page in order for them to access the system.
The issue was experienced in the Dockerized image with Nginx proxy server, I did not try it on the direct JAR installation.
Versions where the issue was experienced 7.45 and 7.46. I did not try it on different versions.