Kibana Caching not working for Chrome

[k9a8r7e6n5]

Kibana version:
6.5.4
Elasticsearch version:

Server OS version:

Browser version:
Chrome 80.0.3987.149 (Official Build) (32-bit)
Firefox 74 (64-bit)
Browser OS version:

**Original install method (e

.g. download page, yum, from source, etc.):**

Describe the bug:
For first time login/load Kibana Discover page, it takes about 40s or more using Chrome.
A new plugin added by our project, and the switching between Discover page and the new plugin page takes 32s or so using Chrome.
The bundle files won't be cached, and every time browser requests for the bundle files and returns 200 OK.
However, with Firefox, after first time request for bundle files returned with 200 OK, later requests will return with 200 OK, and are retrieved from cached. Thought this is the fix provided by #15880.
Just wondering why this fix is not working in Chrome but in Firefox?
Is there any other parameters to set to improve for Chrome?
[See the traffics for chrome & firefox network, sth went wrong while uploading snapshots.]
Chrome traffic:

commons.bundle.js | 200 | script | :32061/bundles/app/kibana/bootstrap.js:71 | 335 KB | 448 ms
-- | -- | -- | -- | -- | --
commons.style.css | 200 | stylesheet | bootstrap.js:29 | 33.8 KB | 304 ms
commons.bundle.js | 200 | script | bootstrap.js:71 | 335 KB | 427 ms
commons.style.css | 200 | stylesheet | :32061/bundles/app/kibana/bootstrap.js:29 | 33.8 KB | 189 ms
commons.bundle.js | 304 | script | :32061/bundles/app/kibana/bootstrap.js:71 | 276 B | 45 ms
commons.style.css | 200 | stylesheet | bootstrap.js:29 | 33.8 KB | 200 ms
commons.bundle.js | 200 | script | bootstrap.js:71 | 335 KB | 485 ms
commons.style.css | 200 | stylesheet | :32061/bundles/app/searchguard-customerror/bootstrap.js:29 | 33.8 KB | 349 ms
commons.bundle.js | 200 | script | :32061/bundles/app/searchguard-customerror/bootstrap.js:71 | 335 KB | 1.38 s
commons.style.css | 200 | stylesheet | :32061/bundles/app/kibana/bootstrap.js:29 | 33.8 KB | 203 ms
commons.bundle.js | 200 | script | :32061/bundles/app/kibana/bootstrap.js:71 | 335 KB | 401 ms
commons.style.css | 200 | stylesheet | bootstrap.js:29 | 33.8 KB | 163 ms
commons.bundle.js | 200 | script | bootstrap.js:71 | 335 KB | 413 ms

Firefox traffic:
_```

304	GET	10.9.245.183:32061	bootstrap.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	vendors.bundle.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	commons.bundle.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	kibana.bundle.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	bootstrap.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	vendors.bundle.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	commons.bundle.js	script	js	cached	0 B
200	GET	10.9.245.183:32061	sbc_overview.bundle.js	script	js	cached	0 B

Thanks a lot for your support!

**Steps to reproduce:**
1.
2.
3.

**Expected behavior:**

**Screenshots (if relevant):**

**Errors in browser console (if relevant):**

**Provide logs and/or server output (if relevant):**

**Any additional context:**

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[tylersmalley]

I would expect a 304 from the cached assets, not a 200. Are you hitting Kibana directly or do you have a load-balancer in place?

[k9a8r7e6n5]

I would expect a 304 from the cached assets, not a 200. Are you hitting Kibana directly or do you have a load-balancer in place?

We use envoy as load balancer.
We are trying to decrease the loading time when switching sections (like between Discover and our own plugin pages) in Kibana.
Seems the cache mechanism only works in firefox but not in Chrome.
Any clue it only works in firefox or any other way we can try to decrease the switching time?

Thanks a lot!

[orgads]

I have the same issue with nginx. Chrome loads everything while FireFox uses the cache.

[tylersmalley]

I am going to close this as there has been a lot of effort to resolve any issues in terms of browser caching. However, let me know if you're still seeing this in 7.8.

One "gotcha" is that Chrome will not cache assists that are served over SSL with a self-signed certificate.