I can't find anything wrong... and yet there is "something" wrong.
Also:
Hmm... I missed that, the content seems to be schema. It's never loaded, I don't know why it's even there.
However, I don't think removing it will change manifest.json behavior, I'll test it.
In the manifest.json file, there is one ātabā in the code; at the start of line:
"start_url": "/",
Try changing that ātabā to just spaces.
[fine tooth comb aināt got nothinā on me]
I'll change it, but it seems the problem isn't the content itself, check my 1st test below.
2 tests with wp-json removed:
Here I accidentally put /manifest.json/
instead of /manifest.json
resulting 404, it starting new ssl handshake. The word manifest.json is cursed, man.
After being corrected
[sticks and stones won't break me]
Do you want to use a bigger hammer?
Cuz Iām down with that path.
Ready?
[ I gots hammers galore ]
I put smashingmagazine html on my site, guess what, json still weird.
So it's established the problem isn't on the html, but on the nginx, or ssl?
Sigh... I'll just reload the VPS from snapshot. Let's do it.
Hammer #1:
Modify the mime types:
#application/json json;
text/plain txt json;
hmmā¦
Maybe browsers (even the emulated ones) will differ loading the manifest.json file until all other content is loadedā¦ ? ? ?
Which would mean that there is no way to better this [into a single load].
I donāt know how browsers act/react to manifest files.
Thatās something to look into.
In the meantime, I will try loading a copy of your manifest file into one of my test sites and report back with that outcome.
Done, nothing changed
I think browser will deffer json looking from the waterfall on GTMetrix, no matter how much the resource, always loaded late. The thing is, only my site that requiring that new SSL handshake. Other sites that I tested load manifest.json normally.
smashingmag
https://gtmetrix.com/reports/www.smashingmagazine.com/bxHDHUJz
menshealth
https://gtmetrix.com/reports/www.menshealth.com/fGGLH1YX
Similar problem with mine :
realsimple com
https://gtmetrix.com/reports/www.realsimple.com/0NDzbZim
independent uk
https://gtmetrix.com/reports/www.independent.co.uk/QXYHYDds
time
https://gtmetrix.com/reports/time.com/YYfH7ptL
WOW, it turns out this is common problem!
So do we blame the server or the client?
[or both!]
I must be missing something.
I canāt get the manifest file to be served:
It seems Chrome bug, don't how several sites able to work around it.
I tried using manifest.webmanifest
, this is similar to manifest.json
It loaded the same.
I can't even preload it. Preloading json, whether using html preload or server push end up similar. The file successfully loaded, but the content not used. There's a workaround for it, but I don't know if it's good
Load improvement without manifest.json is around 300ms, from 1.1s-1.3s to 800ms. And I'm only use it to load Chrome Android favicon conditionally. So I guess I'll try to inline it, although in the past it will result more resource loaded. I think it's better 1 more resource loaded rather than adding new SSL handshake.
Which one is this?
Blocked here too, but it seems because your CSP content security policy setting. https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
On your dev tool you can see it (blocked:csp)
Thatās definitely the right place! Thanks.
But I canāt seem to give it the right settings to be allowed - LOL
OK I get the same problem - two TLS connections.
Maybe exclude that json from that header? or disable the header for testing.
Yup, Chrome bug then. Lol.
Another thing is, manifest.json not loading on Firefox, as FF have its own manifest file and won't adopt manifest.json
But for me this is actually ok if it's loaded fine, because I intended it just from Chrome. lol
Well that was fun!
Remember kids: All work and no play makes Jack a dull boy
So never stop playing around!
-Cheers from Miami
Yeah, I guess this conclude it. Thanks for the company man, it was fun.
Good day, cheers from Indonesia
@rg305
Hi, can you remove my site name from these reply of yours?
https://community.letsencrypt.org/t/resource-loading-require-new-ssl-connection/106774/12
https://community.letsencrypt.org/t/resource-loading-require-new-ssl-connection/106774/2
Also, is it okay for me to remove my siteās name at the top thread, as this is production site.
Thanks
Yes you can remove the site name from this topic; it doesnāt bear any significant relevance on the problem.
Iāve removed it from my posts.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.