You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WaitPageInterceptor uses the identity of the current user and sends another request to start the long process. This implementation cannot work with HTTPS.
The result of using this is that the long process is never started and the user is blocked on the wait page.
A workaround for now it to use Apache HTTP Server and ProxyPass so that Apache process the secured connection and the Java server (ex: Tomcat) will process regular HTTP requests allowing the session id to be stolen by WaitPageInterceptor.
The text was updated successfully, but these errors were encountered:
An actual fix is possible, but it involves having a strict wait page code and so that the browser sends a request that will start the long process.
This breaks everything so a new annotation would be required.
The
WaitPageInterceptor
uses the identity of the current user and sends another request to start the long process. This implementation cannot work with HTTPS.The result of using this is that the long process is never started and the user is blocked on the wait page.
A workaround for now it to use Apache HTTP Server and ProxyPass so that Apache process the secured connection and the Java server (ex: Tomcat) will process regular HTTP requests allowing the session id to be stolen by
WaitPageInterceptor
.The text was updated successfully, but these errors were encountered: