[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Google sites don't work


  • To: debian users <debian-user@lists.debian.org>
  • Subject: Re: Google sites don't work
  • From: Kent West <westk@acu.edu>
  • Date: Mon, 2 Aug 2021 14:00:06 -0500
  • Message-id: <[🔎] CAByJ6DFML7zkiJJaAkceX_1zYW2XRcU+Zo6vcHqd_Dp6CiDvuQ@mail.gmail.com>
  • Reply-to: kent.west@acu.edu
  • In-reply-to: <[🔎] 20210802145147.343eef23@trisector>
  • References: <[🔎] CH0PR01MB690853DC77745FF03C8887F592ED9@CH0PR01MB6908.prod.exchangelabs.com> <[🔎] YQYXJ8mGRTPZltF8@wooledge.org> <[🔎] CH0PR01MB69088AE7DC1A72EB65FB2E4792EE9@CH0PR01MB6908.prod.exchangelabs.com> <[🔎] 36dca4d5-0a3a-9ec2-c732-3c22467a34a4@mail.com> <[🔎] CH0PR01MB6908E86F741EB43705B8B73892EE9@CH0PR01MB6908.prod.exchangelabs.com> <[🔎] CAByJ6DHpFCAW-JXRY-z_r0N+8+Xa8ZeFoDSZc8TymsrhHVrCoQ@mail.gmail.com> <[🔎] 20210802145147.343eef23@trisector>



On Mon, Aug 2, 2021 at 7:52 AM Ivan Krylov <krylov.r00t@gmail.com> wrote:
> Similar problem here, only with Google sites like Gmail, Docs, and
> Chat (via a[n?] university/Google system).

Interesting. Do you see any relevant errors if you press F12 and take a
look at the _javascript_ console on the affected pages, compared to the
unaffected pages? What about the Network tab, any failed requests there?

--
Best regards,
Ivan


When press F12, and then click on the "Console" tab, I get the following, which means nothing to me:

Some cookies are misusing the recommended “SameSite“ attribute 105
Some cookies are misusing the recommended “SameSite“ attribute 24
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
Empty string passed to getElementById(). 3 m=b:1168:137
Empty string passed to getElementById(). 6 m=b:1168:137
Empty string passed to getElementById(). 2 m=b:1168:137
Empty string passed to getElementById(). 2 m=b:1168:137
Empty string passed to getElementById(). 9 m=b:1168:137
Empty string passed to getElementById(). m=b:1168:137
Empty string passed to getElementById(). m=b:1168:137
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Empty string passed to getElementById(). 6 m=b:1168:137
Empty string passed to getElementById(). 3 m=b:1168:137
Empty string passed to getElementById().


Also, another symptom; generally, if I restart the computer, and fire up Firefox, and go to the offending sites, they'll work for 15, 30 minutes, and then start complaining about not being able to connect, and I can no longer go directly to the URLs for those pages. Clearing the cache/cookies doesn't help, 

but just now when I tried clearing cache/cookies again, and still had the F12 Console open, I'm seeing things like this:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://ssl.gstatic.com/dynamite/images/cleardot.gif?zx=aojuhxxm7pdi. (Reason: CORS request did not succeed).

--
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

Reply to:
  • debian-user@lists.debian.org
  • Kent West (on-list)
  • Kent West (off-list)

  • References:
    • Google sites don't work
      • From: "Kleene, Steven (kleenesj)" <kleenesj@UCMAIL.UC.EDU>
    • Re: Google sites don't work
      • From: Greg Wooledge <greg@wooledge.org>
    • Re: Google sites don't work
      • From: "Kleene, Steven (kleenesj)" <kleenesj@UCMAIL.UC.EDU>
    • Re: Google sites don't work
      • From: john doe <johndoe65534@mail.com>
    • Re: Google sites don't work
      • From: "Kleene, Steven (kleenesj)" <kleenesj@UCMAIL.UC.EDU>
    • Re: Google sites don't work
      • From: Kent West <westk@acu.edu>
    • Re: Google sites don't work
      • From: Ivan Krylov <krylov.r00t@gmail.com>
  • Prev by Date: Re: `pv` rates (was: burn iso to usb)
  • Next by Date: Re: burn iso to usb
  • Previous by thread: Re: Google sites don't work
  • Next by thread: Updating kernels impossible when /boot is getting full
  • Index(es):
    • Date
    • Thread