Bootstrap: Caching problems still exist on v4.1.1 docs

[sts-ryan-holton]

@mdo I'm still experiencing this problem, cleared browser cache multiple times, have been checking throughout the day, in particular on this page is a good test -> https://getbootstrap.com/docs/4.1/components/carousel/

the indicators for the carousel. Try clearing your browser cache, it'll then work, but refresh normally after that and cursor: pointer is missing which I assume is related to some additional cache problems?

[sts-ryan-holton]

@mdo any update on this?

[mdo]

Every page I've tested, now across two countries and multiple devices (sorry, I've been traveling!), hasn't had an issue with redirects, stale components, or the search form. Very few people seem to be having this issue, too, as evidenced by the referenced issues here and in your original one. I'm not sure what else I can do as I already purged CloudFlare's cache on our end last week.

[sts-ryan-holton]

@mdo I've just done some experimenting, clearing the browser cache and then normally reloading the browser (what most devs are likely to do) doesn't actually clear the cache on the Bootstrap docs for some reason.

I found, that if I clear my browser cache and then completely close the browser and reopen the browser it then manages to show the correct version of Bootstrap 4.1.1

Tested on Google Chrome on Mac

Right click + inspect element, right click the refresh button and choose to clear the cache, then restart the browser.

I've never had to do this before, and based on the issues referenced above I'm sure others are finding this difficult too, maybe we could consider letting people know?

[sts-ryan-holton]

@mdo

Weirdly, I just noticed....

Try this...

Go to http://getbootstrap.com/ and it will load the new version.

But head to https://getbootstrap.com/ (secure) and it loads the older version.

Also, the search still points to 4.1.0

[rafalp]

I can confirm that https points to Bootstrap 4.1.0 whereas http points to 4.1.1

[sts-ryan-holton]

Weird behaviour, most new people to bootstrap are likely to google for Bootstrap and click the link pointing to https whereas us developers and the Bootstrap dev team are likely to type getbootstrap.com into the URL and thus not likely experience the issue.

[wolfy1339]

There is an http to https redirect, so I'm not sure how you got that.
I don't experience any issue at all with the docs. It displays the right version

[sts-ryan-holton]

@wolfy1339 simply typed in the URL getbootstrap.com - didn't get redirected at all, this issue is still present

[rafalp]

There is an http to https redirect, so I'm not sure how you got that.

This is false. I'm not being redirected at all.

[wolfy1339]

I still can't reproduce at all even on plain HTTP

[rafalp]

What kind of caching is employed? Perhaps european ussers are experiencing the issue because we hit different spot in CDN?

[wolfy1339]

Cloudflare has a cache in front of the website, and that has been purged. Could this possibly be related to workbox?

[sts-ryan-holton]

@wolfy1339 Possibly? Seem to be getting an error with the service worker when I refresh the page? Also, the last time it received was back in early April? Bootstrap 4.1.1 was released after that?

[mdo]

Is this service worker related or something @XhmikosR? Only Chrome seems affected for some folks here?

[XhmikosR]

@mdo: I have no idea since I was never able to reproduce...

/CC @gauntface @addyosmani @Lyricalz : do you happen to have any ideas if it's indeed service worker related?

[coliff]

for what its worth- I'm in Japan and can report the following is true for me;

• http://getbootstrap.com is not redirecting to https://getbootstrap.com
• https://getbootstrap.com/ is showing 4.1.0
• http://getbootstrap.com/ is showing 4.1.1
• Docs search results always shows 4.0 (even from a 4.1 docs page)

Tested on Windows 10 Chrome 66 and macOS Chrome 66

[XhmikosR]

The https redirect does not happen because @mdo never enabled this.

@mdo: somewhere you broke the docs when you changed the assets.

1. the 4.1 docs (at least) are missing the brand images
2. You are missing the vendor JS files thus leading to an error which might explain this
   NetworkError: Failed to load worker script at "/assets/js/vendor/workbox-sw.js"

[MikeyBeLike]

If it's only happening on https, then it's definitely the service worker is still caching the original redirect response from /.

This file gives me a 404 on incognito: https://getbootstrap.com/assets/js/vendor/workbox-sw.js probably why the service worker won't update

I get 4.1.1 on Chrome though

[coliff]

@XhmikosR - oh yep, I see: https://github.com/twbs/bootstrap/issues/23262
It'd be good to have always on HTTPS with HSTS.

[XhmikosR]

I've bugged Mark countless times and I plan to do so until everything is
https only :). But please don't mix different issues

On Fri, May 11, 2018, 13:47 Christian Oliff [e-mail]
wrote:

@XhmikosR https://github.com/XhmikosR - oh yep, I see: #23262
https://github.com/twbs/bootstrap/issues/23262
It'd be good to have always on HTTPS with HSTS.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/issues/26441#issuecomment-388328822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtXMkmmCnSp4-UlgEdJtIHNspP4iBks5txWwwgaJpZM4Tvt4E
.

[sts-ryan-holton]

Still experiencing Cache problems, any idea when this will be fixed?

[coliff]

hey @sts-ryan-holton - open Chrome Devtools, open Application tab and then Application > Clear Storage. Then tap the 'Clear site data' button to wipe service worker storage etc. That'll fix it for you.

[sts-ryan-holton]

@coliff Awesome, that seemed to work. How are we going to do this for other users though? Most users aren't going to do it that way? Is there a way to automate this on new releases?

This seems to fix the docs search too.

[MikeyBeLike]

@XhmikosR I can revisit the service worker PR and implement a proper "update" feature for new releases?

[XhmikosR]

Please do so and ping me!

On Mon, May 14, 2018, 13:55 Michael Olukoya [e-mail]
wrote:

@XhmikosR https://github.com/XhmikosR I can revisit the service worker
PR and implement a proper "update" feature for new releases?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/issues/26441#issuecomment-388776486,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVteJ4ltIlUsanfMNMK7GsMK6B5jh9ks5tyWKegaJpZM4Tvt4E
.

[XhmikosR]

@Lyricalz: while at it, how about we cache bust the workbox-sw.js? Not sure what workbox does out of the box, but it makes sense. Maybe they have an API for this?

[sts-ryan-holton]

Any update on this? @XhmikosR @Lyricalz

[XhmikosR]

@mdo needs to update the docs to fix the current issue.

[mdo]

Hoping with the close of #23262 this should be resolved. Can folks verify?

[XhmikosR]

Mark, please check my comments above. You missed copying all the JS assets
with the docs refactoring.

On Sun, May 20, 2018, 23:32 Mark Otto [e-mail] wrote:

Hoping with the close of #23262
https://github.com/twbs/bootstrap/issues/23262 this should be resolved.
Can folks verify?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twbs/bootstrap/issues/26441#issuecomment-390509961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVVtZvzzPzf36WKbLP9tnAKb3V9sYGmks5t0dLBgaJpZM4Tvt4E
.

[sts-ryan-holton]

@mdo Going to http://getbootstrap.com/ does not redirect me

[XhmikosR]

@Lyricalz: any updates?

BTW, I was thinking, can't we switch to local hosting the workbox files like in older versions but still use injectManifest()?

[mdo]

I enabled the redirection, but had to disable it as the https enforcement affects our Themes and Jobs sites, breaking our iframes and more. Still have to dig into that more.

[XhmikosR]

@mdo: please let me know if the details on Slack so that we can get this sorted ASAP. There are still a couple more issues we need to fix in docs.

[mark-zacharias]

what in the actual fuck. remove your service worker until this is fixed. It causes much pain!
I can see in the dev tools that the service worker claims to have last received data on 11/24/2017, 3:34:14 PM.

[XhmikosR]

Chill out dude. This should fix it #26594

[MikeyBeLike]

@mark-zacharias Why don't you contribute then?