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

Various HTTP errors trying to access both TR and ED versions #440

Closed
domenic opened this issue Aug 10, 2024 · 4 comments
Closed

Various HTTP errors trying to access both TR and ED versions #440

domenic opened this issue Aug 10, 2024 · 4 comments

Comments

@domenic
Copy link

domenic commented Aug 10, 2024

https://w3c.github.io/jlreq/ in Firefox gives the error

GET https://www.w3.org/Tools/respec/respec-w3c NS_ERROR_DOM_CORP_FAILED

The resource at “https://www.w3.org/Tools/respec/respec-w3c” was blocked due to its Cross-Origin-Resource-Policy header (or lack thereof). See https://developer.mozilla.org/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)#

https://www.w3.org/TR/jlreq/ in both Firefox and Chrome gives tens of 429 errors for each image, e.g.

GET https://www.w3.org/TR/jlreq/images/img2_4_3.png 429 (Too Many Requests)

@r12a
Copy link
Contributor

r12a commented Aug 10, 2024

Seems to be working ok for me on Firefox and Chrome. If it's still happening for you, could it be a mirroring problem?

@domenic
Copy link
Author

domenic commented Aug 12, 2024

The first error about CORP seems to have been resolved. The second with 429s on the TR copy is still occurring for me... I'll note that I'm getting Cloudflare-verified each time which is a bit strange.

@himorin
Copy link
Contributor

himorin commented Aug 13, 2024

@domenic if you encounter Cloudflare-verified page many times - by means unusual times in normal site browsing, you may get Ray ID (some sort of case ID in CF naming) shown on verification or error page. With that you may consult with W3C systems team, I suppose (please note, I'm not familiar with case handling operation in deep...).
I believe that is what we can say (at most) at this moment.

@himorin
Copy link
Contributor

himorin commented Sep 5, 2024

closing. I heard from systeam that there was system configuration update (on misconfiguration) at 28 Aug, and this 429 should be resolved.
If you encounters similar display error, please let me know.

@himorin himorin closed this as completed Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants