Project

General

Profile

Actions

Bug #27156

closed

Installation with numbers in FQDN fails.

Added by Richard Stempfl almost 5 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

If I want to install and use the name just.anexample.123 the installation fails because the proxy is not found.
If I call the website with it I get a 400 error.
But if I enter the ip I can call the website.

Log:

Foreman_smartproxy[just.anexample.123](provider=rest_v3): Making get request to https://just.anexample.123/api/v2/smart_proxies?search=name=%22just.anexample.123%22
[DEBUG 2019-06-25T14:22:13 main] Foreman_smartproxy[just.anexample.123](provider=rest_v3): Received response 400 from request to https://just.anexample.123/api/v2/smart_proxies?search=name=%22just.anexample.123%22
[ERROR 2019-06-25T14:22:13 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[orcha.rhino.441]: Could not evaluate: Proxy just.anexample.123 cannot be retrieved: unknown error (response 400)

Actions #1

Updated by Zach Huntington-Meath about 4 years ago

Using numbers as a top level domain is not generally supported. If you still have a log from the foreman server would you mind posting it?

Actions #2

Updated by Richard Stempfl about 4 years ago

Zach Huntington-Meath wrote:

Using numbers as a top level domain is not generally supported. If you still have a log from the foreman server would you mind posting it?

I have generated a new one. What part do you need?

Actions #3

Updated by Ewoud Kohl van Wijngaarden over 3 years ago

  • Status changed from New to Rejected

It's illegal data according to RFCs so this isn't really something that should be supported. Patches to support this may be accepted, but this is not a valid bug report.

Actions

Also available in: Atom PDF