Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs are not loading #12665

Closed
arashrasoulzadeh opened this issue Aug 14, 2018 · 16 comments
Closed

docs are not loading #12665

arashrasoulzadeh opened this issue Aug 14, 2018 · 16 comments

Comments

@arashrasoulzadeh
Copy link

Bug, feature request, or proposal:

docs page is not working

What is the expected behavior?

What is the current behavior?

What are the steps to reproduce?

Providing a StackBlitz reproduction is the best way to share your issue.

StackBlitz starter: https://goo.gl/wwnhMV

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Is there anything else we should know?

@alex7egli
Copy link

Same issue. I'd say about 75% of the time that I try to go to https://material.angular.io/ it doesn't load. I just see a white screen with console error that https://material.angular.io/main.af62af8dab0824d37bac.js could not load due to a 404.

Today I also got this warning:
DevTools failed to parse SourceMap: https://material.angular.io/ngsw_worker.es6.js.map

@Trent-Matthias
Copy link

Try opening the dev tools in chrome, click on the application tab, then service workers, and check the bypass for network checkbox.

@arashrasoulzadeh
Copy link
Author

what about safari ?

error is :
Safari can’t open the page “https://material.angular.io/”. The error is: “FetchEvent.respondWith received an error: Error: Response not Ok (fetchAndCacheOnce): request for https://material.angular.io/index.html returned response 301 ” (WebKitServiceWorker:0)

@jotatoledo
Copy link

Dup of #11745

@dennis-8
Copy link

It doesn't work on FireFox too.

Corrupted Content Error

The site at https://material.angular.io/components/checkbox/overview has experienced a network protocol violation that cannot be repaired.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

Please contact the website owners to inform them of this problem.

@mpostelnicu
Copy link

i see a blank page 50% of the time, refresh does not help. then suddenly it starts working. then it starts returning again blank page

2main.af62af8dab0824d37bac.js:1 Failed to load resource: the server responded with a status of 404 ()

Xubuntu Linux Chrome Version 68.0.3440.106 (Official Build) (64-bit)

@jelbourn
Copy link
Member

A new version has been deployed that should eliminate this problem.

@timmyrosen
Copy link

The docs site has been unreachable for me now for a few days.

Here is the console output:

Uncaught (in promise) Error: Response not Ok (fetchAndCacheOnce): request for https://material.angular.io/index.html returned response 301 
    at PrefetchAssetGroup.<anonymous> (ngsw-worker.js:576)
    at Generator.next (<anonymous>)
    at fulfilled (ngsw-worker.js:304)
(anonymous) @ ngsw-worker.js:576
fulfilled @ ngsw-worker.js:304
A bad HTTP response code (404) was received when fetching the script.
Failed to load resource: net::ERR_INVALID_RESPONSE

I can't clear the service worker or storage either because the site path is just ://

@alex7egli
Copy link

Still having the same issue as before. The page is just blank with the same 404 error.

@jelbourn
Copy link
Member

You may have to clear the service worker one last time to get rid of your cached version.

@arashrasoulzadeh
Copy link
Author

how ? im using safari

@timmyrosen
Copy link

@jelbourn I can't even do that. See these attached images of how it looks in chrome dev tools

skarmavbild 2018-08-22 kl 09 54 50
skarmavbild 2018-08-22 kl 09 55 09

Notice on the Clear Storage tab, the path is just "://"
I'm forced to use the incognito window to read the docs right now

@jelbourn
Copy link
Member

Try using chrome://serviceworker-internals instead of the devtools

@timmyrosen
Copy link

@jelbourn Thanks, that fixed it!

@mackelito
Copy link

What PR fixed this? We have similar issues and looking for a solution..

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants