forked from browserup/browserup-proxy
-
Notifications
You must be signed in to change notification settings - Fork 2
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
BUP spams logs with useless errors "unknown protocol" #472
Milestone
Comments
asolntsev
added a commit
to asolntsev/browserup-proxy
that referenced
this issue
Feb 7, 2025
…Host()` I made it package-private to call from a unit-test.
asolntsev
added a commit
to asolntsev/browserup-proxy
that referenced
this issue
Feb 7, 2025
asolntsev
added a commit
to asolntsev/browserup-proxy
that referenced
this issue
Feb 7, 2025
Merged
valfirst
pushed a commit
that referenced
this issue
Feb 8, 2025
I made it package-private to call from a unit-test.
valfirst
pushed a commit
that referenced
this issue
Feb 8, 2025
valfirst
pushed a commit
that referenced
this issue
Feb 8, 2025
Fixed by #473 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
java.net.MalformedURLException: unknown protocol: accounts.google.com
java.net.MalformedURLException: unknown protocol: googlechromelabs.github.io
java.net.MalformedURLException: unknown protocol: safebrowsingohttpgateway.googleapis.com
java.net.MalformedURLException: unknown protocol: plausible.io
java.net.MalformedURLException: no protocol: 127.0.0.1:36915
To Reproduce
Steps to reproduce the behavior: clone Selenide project and run test
integration.proxy.ChainedProxyTest
.Expected behaviour
Please complete the following information:
Stack trace
The text was updated successfully, but these errors were encountered: