Forums » English support forum »

space after server address (FQDN) leads to error and full stop [0.7.2, bug]

Added by surfer almost 4 years ago

Hi,

When there is space after the server address (FQDN), this leads to an error and full stop [NNTPgrab 0.7.2]

The error is:

The schedular has been paused due to an error:
Unable to detect the IP address belonging to 'newszilla.xs4all.nl ' (servername = newszilla)

This also happens with another illegal character, like a '*'.

Expected behaviour (IMHO):
- NNTPgrab should do a check at the moment the server address is filled out to catch illegal characters and non-existent names. And:
- NNTPgrab should continue to use the other servers, and not stop the whole download process

Thank you for NNTPgrab


Replies

RE: space after server address (FQDN) leads to error and full stop [0.7.2, bug] - Added by Alguno almost 4 years ago

Hi,

When an error in the configuration is detected (like an invalid hostname for the usenet server) it is intentional that the scheduler is being paused automatically.
This is done on purpose so that the user knows (right after start up of the program or when a configuration change happens) that there is an error in the configuration so it can be fixed.

To reduce the chance that the user enters an invalid hostname I could add a filter to the configuration dialog so that only the characters a to z, 0 to 9 and the . are allowed.

RE: space after server address (FQDN) leads to error and full stop [0.7.2, bug] - Added by surfer almost 4 years ago

I believe - en _ are also allowed in hostnames.

RE: space after server address (FQDN) leads to error and full stop [0.7.2, bug] - Added by surfer almost 4 years ago

PS: Wikipedia says:

The Internet standards (Request for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. However, a subsequent specification (RFC 1123) permitted hostname labels to start with digits. No other symbols, punctuation characters, or white space are permitted.

So: a-z, A-Z, 0-9, and -. And of course the dot between the 'labels'.