Bug 491563

Description of problem:
I'm missing flexibility to tell the user somehow about captcha-only webwhois
servers such as some strange and even bigger registries have. For example, the
registries for .es, .gr and .nc are requiring the user to enter a captcha via
http before showing anything. I would like to see jwhois prompting a message,
that this strange registry violates against RFC/whois and that the user has to
go to some URL and to perform the whois/lookup there, e.g.

$ whois <domain>.nc
The domain name registry of .nc unluckily doesn't provide neither a
RFC compliant whois service nor some other kind of whois service that
could be queried without a graphical user interface. Thus this whois
request has to be performed manually using a web browser, please visit
the website: http://www.domaine.nc/en/whois.html
$

In configuration file, something like the following should be suitable IMHO:

--- snipp ---
"\\.nc$" = "www.domaine.nc";

server-options {
  "www\\.domaine\\.nc" {
    webonly = "true";
    webonly-path = "/en/whois.html";
  }
--- snapp ---

Version-Release number of selected component (if applicable):
jwhois-4.0-12

How reproducible:
Everytime, see above and below.  

Actual results:
Missing flexibility to tell the user about captcha-only webwhois servers.

Expected results:
An ugly workaround could be some kind of a lynx-wrapper in before, which knows
the worse top-level-domains and handles exactly that using regular expressions.
But I would like to see this sane solved and in jwhois directly. Maybe we can
hack in such a functionality into jwhois?