Skip to content

HTTPS call causes E500, if cannot resolve DNS record #18

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

Open
tkohegyi opened this issue Dec 14, 2023 · 1 comment
Open

HTTPS call causes E500, if cannot resolve DNS record #18

tkohegyi opened this issue Dec 14, 2023 · 1 comment

Comments

@tkohegyi
Copy link
Owner

tkohegyi commented Dec 14, 2023

Internal error (E500) occurs in proxy if DNS record cannot be resolved during a HTTPS call.

Answer (incorrect):
14:05:09.380 [SocketListener0-1] DEBUG n.l.b.p.s.SeleniumProxyHandler - CONNECT: .....
14:05:09.418 [SocketListener0-1] DEBUG n.l.b.p.s.SeleniumProxyHandler - error during handleConnect
java.net.UnknownHostException: No such host is known (....)
14:05:09.422 [SocketListener0-1] DEBUG n.l.b.p.jetty.http.HttpConnection - RESPONSE:
HTTP/1.1 500 java%2Enet%2EUnknownHostException%3A+No+such+host+is+known+.....

In case of HTTP, E404 is used (let say it is correct):
14:03:58.604 [SocketListener0-1] DEBUG n.l.b.p.jetty.http.HttpConnection - RESPONSE:
HTTP/1.1 404 Not Found

quickest test command (if proxy is running on localhost and at port 9092):
curl --insecure -X GET https://no.dns.record -x 127.0.0.1:9092
result: curl: (56) CONNECT tunnel failed, response 500

@tkohegyi
Copy link
Owner Author

This fix addresses it: 89f7761

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

1 participant