hm, for some reason I’m too dumb to get OC running via sslkundenserver.de…
even with your lines from config.php it kept redirecting to http
But I made another test. And from the results it seems for me like the proxy on sslkundenserver.de removes the ETag header. So the host that hosts your OC generates the ETag header and delivers it to the ssl-proxy… but then the proxy removes it…
My test was to retrieve a jpg from my webspace with curl and let the headers write into a simple textfile.
If you’re on Linux you can reproduce it with curl command. If not you also can reproduce it via ssh access to your webspace:
retrieve image via https and sslkundenserver.de:
curl -D headers_https.txt https://www.sslkundenserver.de/www.mydomain.tld/test/image.jpg > image_https.jpg
retrieve image via http and without sslkundenserver.de:
curl -D headers_http.txt http://www.mydomain.tld/test/image.jpg > image_http.jpg
This will save the jpg on the one hand in file image_https.jpg and on the other hand in file image_http.jpg
In the headers*.txt files you will see the headers that were transferred between client (curl) and server.
[user@host davdroid-tests]$ ls -la headers_http*
-rw-r–r-- 1 user user 208 13. Sep 21:12 headers_https.txt
-rw-r–r-- 1 user user 271 13. Sep 21:11 headers_http.txt
[user@host davdroid-test]$ grep -i etag headers_http*
—> so the header only was retrieved via http…