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.