-
Notifications
You must be signed in to change notification settings - Fork 110
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
Logout disabled on chrome #46
Comments
I'll have a look, thanks for the report |
@ejouvin , I'm not able to reproduce the issue. Could you provide some kind of log of the http traffic of the logout sequence? Do you notice some kind of HTTP errors? As an example, this is what happen on my side: |
There is no traffic. |
which version of chrome/operating system are you using? |
Windows & Chrome version 55.0.2883.87 (Build officiel) In fact, when access to the Tomcat directly, this is OK. And finally, this is linked to #45 But Under Firefox and IE, no problem. |
I think that you have the same issue as #38, some headers are incorrectly handled by Chrome with your current configuration. |
Hum, seems to be an SSL related issue. But when I put the configuration under a not SSL site, it is OK. It really seems to be an SSL error when self signed But the solution does not solve my error. Moreover I found that I have error when accessing websocket So there is also an error in my Apache configuration. |
Did you check the issue #38? It's based on NGINX but I think the problem is the same, make sure you send the right headers through the proxy. |
I am still stuck. Will try again, hope someone will find the solution ;) |
"Finally" I got it work, not fully as I expected, but for a first step... So for those who will have difficulties, here is what I put in my Apache configuration, thanks to reading on
I did comment the second RewriteRule, because this configuration is shared why other application deployed and not necessary in the same Tomcat. But, this will only work when Lavagna on Tomcat and enabled behind an Apache in http, not in https. I will have to study in order to deploy it under SSL, may be need to activate the SSL ono tomcat also. I close the issue. |
@ejouvin thanks for the comment, we will add your configuration in the documentation :) |
Did you try |
@SitoCH Yes I did try, but no chance. I will give it a try later. |
@syjer Thanks. |
1 year since I try to find a solution. I found a try to make it works on HTTPS for Apache server, but deployed on HTTP in Tomcat. Careful, I change one another thing...
The important part was the wss redirection and the request header modification, for proto and port. |
Perfect, thank you for posting the proxy configuration because at the moment we had only samples for NGINX and it may be really useful for other users. |
Full proxy configuration for proxy with HTTPS
In this case, Lavagna is deployed on Tomcat, on same server than Apache, and aceessible throw http://localhost:8080/lavagna The proxy configuration made Lavagna enabled under https://www.lavagna.dummy.net. It would be easier if I wanted to have https://www.dummy.net/lavagna. A "root" folder is created under /var/www/lavagna, where I put a file robots.txt. For websocket, the trick is there
For the robots.txt file, use directive to order to serve the file frmo the root folder.
Proxy redirect for the other.
Because I expose Lavagna under a sub domain, many things to do. First, change headers.
The first one is for the login page. The redirect URL in argument must be (hman readable) reqUrl=/ and not reqUrl=/lavagna/ (because the root location in Tomcat is /lavagna) The most tricky part was to modify one directive in the HTML. Bad news is that it required to "unzip", modfiy content and then zip.
In this case, I replace by . Like this, all CSS, Javascript call will be on the correct location. And finally I had to change the request header to force the HTTPS. Without this, websocket will fail.
Hope this will help. |
Installed from the last commit, when I access to the application with Chrome, the logout button does nothing.
The text was updated successfully, but these errors were encountered: