-
Notifications
You must be signed in to change notification settings - Fork 6
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
WaitPage annotation does not work with HTTPS #15
Labels
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: