-
Notifications
You must be signed in to change notification settings - Fork 554
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
Webmock fails when making ::Net::HTTP request to ipv6 address #806
Closed
arkadiyt opened this issue
Feb 11, 2019
· 2 comments
· Fixed by DFE-Digital/schools-experience#1640, DFE-Digital/get-into-teaching-app#962, denny/ShinyCMS-ruby#994, DFE-Digital/teaching-vacancies#3030 or xlgmokha/scim-kit#16
Closed
Webmock fails when making ::Net::HTTP request to ipv6 address #806
arkadiyt opened this issue
Feb 11, 2019
· 2 comments
· Fixed by DFE-Digital/schools-experience#1640, DFE-Digital/get-into-teaching-app#962, denny/ShinyCMS-ruby#994, DFE-Digital/teaching-vacancies#3030 or xlgmokha/scim-kit#16
Comments
We had the same issue with IPv6 addresses. We would be happy to provide a patch. |
@JohannaHartmann a patch would be very much appreciated :) |
JohannaHartmann
added a commit
to JohannaHartmann/webmock
that referenced
this issue
Mar 4, 2021
JohannaHartmann
added a commit
to JohannaHartmann/webmock
that referenced
this issue
Mar 4, 2021
JohannaHartmann
added a commit
to JohannaHartmann/webmock
that referenced
this issue
Mar 4, 2021
JohannaHartmann
added a commit
to JohannaHartmann/webmock
that referenced
this issue
Mar 4, 2021
bblimke
added a commit
that referenced
this issue
Mar 5, 2021
Fix: Handle IPv6 hostname correctly (closes #806)
This was referenced Mar 7, 2021
This was referenced Mar 8, 2021
Closed
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro case:
gives me (the extra stacktrace parts are because I'm running it on an existing project):
This is on webmock
3.5.1
and ruby2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]
The text was updated successfully, but these errors were encountered: