Skip to content
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

'InvalidContent' vs 'ConnectionError' #416

Open
eserte opened this issue Jul 17, 2021 · 4 comments
Open

'InvalidContent' vs 'ConnectionError' #416

eserte opened this issue Jul 17, 2021 · 4 comments

Comments

@eserte
Copy link

eserte commented Jul 17, 2021

t/14_dns_client_errors.t fails on some of my smoker systems:

#   Failed test 'Correct code ConnectionError code'
#   at t/14_dns_client_errors.t line 29.
#          got: 'InvalidContent'
#     expected: 'ConnectionError'
# LWP caller
# Mojo caller

#   Failed test 'Correct code ConnectionError code'
#   at t/14_dns_client_errors.t line 70.
#          got: 'InvalidContent'
#     expected: 'ConnectionError'
# Furl caller
# Looks like you failed 2 tests of 8.
t/14_dns_client_errors.t ................ 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/8 subtests 
@eserte
Copy link
Author

eserte commented Jan 21, 2024

Very probably the reason is the presence of wildcard DNS records on these systems. See also tokuhirom/Furl#128 for more information about this.

Without checking it, the usual fix is to add a dot to the invalid DNS name to make sure that it is not expanded. To simulate a possibly problematic system, one can set on Linux systems the LOCALDOMAIN environment variable to a domain using wildcard DNS records (in the past, bing.com or opensuse.de could be used for this).

@castaway
Copy link
Collaborator

ah thanks! I was just trying to figure out what was going on..

@castaway
Copy link
Collaborator

Hmm, sadly this works on 2/3 of 14_dns_client_errors.t, but not the first one

@eserte
Copy link
Author

eserte commented Jan 21, 2024

Do you have a diff or so? I could try it on my systems.

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

2 participants