-
-
Notifications
You must be signed in to change notification settings - Fork 282
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: address possible removal in cloud providers #1324
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I'm also thinking of removing Remote TestKit; their website hasn't worked since around June of last year.
btw, @eglitise which website? |
That... is odd, because whenever I try to access this website (including just now), it returns 403 Forbidden. Even tried multiple browsers and locations. Maybe there's some geoblocking going on that wasn't present early last year? |
Hm, possibly yes. I saw that GDPR made some websites (by Japanese companies) shut down from EU countries. Could it be related if your access was from around there |
hm, then we probably need to address such limitations somehow (maybe in README...?, no idea right now) |
I have confirmed with VPN about the 403. Maybe we could do something, or request them to mention like this info on the UI (if needed) |
If this is indeed due to GDPR, I think the least they could do is change that HTTP 403 to HTTP 451 😅 |
I think it would be nice to address possible removal in case they are not compatible with our inspector.
#391