Feature #10129: More descriptive error message for failed net/http requests

• Status: Assigned
• Assignee: akr (Akira Tanaka)
• Target version: -

[xshay (Xavier Shay)]

Hello,
I would like to propose the following patch:

Before

2.1.2 :003 > Net::HTTP.get(URI.parse("https://arsrtrtrstsrt.com/arstr"))
SocketError: getaddrinfo: nodename nor servname provided, or not known

After

2.1.2 :003 > Net::HTTP.get(URI.parse("https://arsrtrtrstsrt.com/arstr"))
SocketError: Failed to open TCP connection to arsrtrtrstsrt.com:443 (getaddrinfo: nodename nor servname provided, or not known)

I have an implementation with test at https://github.com/ruby/ruby/pull/700

Thank you for your consideration,
Xavier

[xshay (Xavier Shay)]

• File net-http-error-message.diff net-http-error-message.diff added

Attaching diff, possibly more useful than github PR.

[nobu (Nobuyoshi Nakada)]

• Category set to ext
• Status changed from Open to Assigned
• Assignee set to akr (Akira Tanaka)
• Target version set to 2.2.0

Shouldn't Socket methods raise more descriptive messages?

https://github.com/nobu/ruby/compare/socket-error-message

[normalperson (Eric Wong)]

[e-mail] wrote:

Shouldn't Socket methods raise more descriptive messages?

https://github.com/nobu/ruby/compare/socket-error-message

Yes. I think the EAI_SYSTEM case should also include host/port in the
error message, too.

[naruse (Yui NARUSE)]

Nobuyoshi Nakada wrote:

Shouldn't Socket methods raise more descriptive messages?

https://github.com/nobu/ruby/compare/socket-error-message

example domain should use *.invalid
http://tools.ietf.org/html/rfc2606

[naruse (Yui NARUSE)]

• Target version deleted (2.2.0)