The operating system my web server runs on is (include version):Ubuntu 16.04 32
My hosting provider, if applicable, is: Digital Ocean
I can login to a root shell on my machine (yes or no, or I don’t know): YES
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): Latest version (installed on Oct 2019
When loading my site, on any page of it, manifest.json always requiring new SSL connection to download, check my screenshot
This is from GTMetrix screenshot. Checking with Google Chrome resulting the same. Testing other website, manifest json loading normally without requiring new SSL connection. Is there anything I can do to fix this problem?
I just changed it, not working, still new ssl handshake. Other resource on header loaded properly, only this one, manifest.json on any page, that always requiring new ssl handshake. I don’t do anything weird with Nginx config.
Is there a way to force new ssl handshake for certain resource? I’ll check it on my rig if there’s such thing like that.
Edit, I can only give you tea because the answer is wrong
Perhaps your main config is limiting the number of files per connection; thus requiring multiple connections.
Simple test:
[let’s not mess with production - lol]
copy the html file to another file
test that new file has the exact same problem
change the order where the json file is loaded [up or down - makes no difference]
restest new modified file
reply with that result
Unless the gzip thing did the trick!
[I’d be surprised]
Perhaps your main config is limiting the number of files per connection; thus requiring multiple connections.
The weird thing is, you might not believe this, at all pages, so there are different counts of resources that get loaded, manifest.json always requires new ssl handshake, and in waterfall chart it's always loaded late, so this json is not always loaded on the same sequence, different counts of images loaded before this.
I'll try to create HTML file with json file moved to bottom.
If it won’t answer the question directly… we will beat the answers out of it!
Haha, you're right, this is what I often do, pretty tiring though. But can't do anything else since I can't even find this problem on Google. Cursed VPS/site
Here's the json at bottom, not loading at all.
Maybe there's requirement manifest json have to be at header?
Before this I also tried adding blabla.json next to manifest.json, only the first json loaded (manifest.json)
Is there rule that on site only allowed 1 json?
There don’t really even look close to the same:
-rw-r–r-- 1 root root 141189 Nov 20 00:49 index.html
-rw-r–r-- 1 root root 98170 Nov 20 00:32 test.html
As long as it can “reproduce” the problem…
Let’s continue.