Defect #5443
closed
redirect problem w/Chrome and SSL
0%
Description
I have a weird problem, not sure if this is due to Redmine but...
I have my Redmine configured in apache w/passenger. In firefox when I go to:
https://host/redmine and https://host/redmine/ both work fine
but when I do the same in Google Chrome
https://host/redmine works fine but https://host/redmine/ render ruby source code.
What is interesting, subsequent pages e.g. https://host/redmine/my/page work.
And, if I take down SSL (move the config to port 80) then all things work, any ideas?
Updated by Felix Schäfer over 14 years ago
See in your apache and redmine (REDMINE_DIR/logs/production.log) logs if there is anything special about the Chrome requests. If you know how to do it, please also provide a header dump of either URIS (with and without the trailing /) (you can get a header dump e.g. with curl -v)
Updated by Radek Antoniuk over 14 years ago
can't do that for two reasons:
1 - the problem does NOT occur with different browsers (so curl invocation won't help, because even with links it works fine)
2 - i cannot dump raw headers because the machine this is installed on is using KVM and tcpdump and other stuff doesn't work there:/
I'll try to duplicate this behavior on my second instance of redmine though
Updated by Felix Schäfer over 14 years ago
Oh, I meant the http headers, something like this:
$ curl -vI https://orga.fachschaften.org * About to connect() to orga.fachschaften.org port 443 (#0) * Trying 129.217.6.42... connected * Connected to orga.fachschaften.org (129.217.6.42) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): .....
Updated by Radek Antoniuk over 14 years ago
I know that you meant HTTP headers ;-)
But they are useless if you are connecting with curl instead of Chrome, right?
curl -vI https://x.y.z/redmine * About to connect() to x.y.z port 443 (#0) * Trying 1.2.3.4... connected * Connected to x.yz. (1.2.3.4) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS alert, Server hello (2): * SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed * Closing connection #0 curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed More details here: http://curl.haxx.se/docs/sslcerts.html
Updated by Radek Antoniuk over 14 years ago
- Status changed from New to Resolved
ok, forget it.
cleaning the cache three times in chrome fixed it.
i'm starting to dislike chrome...
Updated by Felix Schäfer over 14 years ago
- Status changed from Resolved to New
I just wanted to see if there was something fishy about the redirect from redmine to redmine/. Anyway, what version of chrome, and could you try a different version? Is it only from one machine, or also other machines? Can you identify what file is rendered? (or just paste a screenshot here, I'll look for it myself.)
Updated by Radek Antoniuk over 14 years ago
I think nothing.My idea is that was caused by a misconfiguration of Ruby on the server and chrome cached that.
Nothing was renderred, I got the plain dispatch.rb file out of the browser :)
Updated by Felix Schäfer over 14 years ago
- Status changed from New to Closed
- Resolution set to Invalid
Oh, sorry, I hadn't seen your last post before mine. I'll mark this as closed if all is well now :-)