Redmine

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)

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

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):
..... 

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

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 :)