OpenSRS::Client is for talking over port 50000
OpenSRS::XML_Client is for talking over port 55000
AFAIK, new functionality will only work via the XML base, so you'll have to
move over to it for the new functions anyway.
If you're setting up the new client (say, for testing) you should use the
complete client code - OpenSRS.conf has changed enough since v2.0.3 that it
just won't work properly with v2.3x - which may be causing your errors (I'm
guessing here that you're using your old OpenSRS.conf file with the newer
code....)
Charles Daminato
Product Manager (ccTLDs)
Tucows Inc. - [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Noah Couture
> Sent: February 7, 2001 2:26 PM
> To: [EMAIL PROTECTED]
> Subject: renewals and transfers
>
>
> Hi folks,
>
> I've been using a custom perl script in place of the cgi's for several
> months now, and we want to add in the renewal and transfer
> functionality. What i'm trying to figure out is: do I have to figure out
> how to use OpenSRS::XML_Client, or will OpenSRS::Client work? Also, will
> the latter go away at some point?
>
> In order to test the new api, I installed the cgi's and tried them out. I
> had REMOTE_PORT set to 50000 (since i'd been using ::Client for my custom
> script). With this setting, the verify_install.cgi (and the others) give
> me this error: 'ERROR: Unable to login to server: 401 Unrecognized
> Peer'. Looking through the code, this makes sense sites ::XML_Client
> wants to see a different signature in the handshake. Ok, so the really
> annoying part is that if change this to 55000, all the cgi's simply bomb
> out. The output of verify_install.cgi script for example, is truncated
> just where the login test is supposed to be. The renew.cgi that I was
> testing just gives me the typical terminated before sending headers 500
> error.
>
> Any idea what i'm missing?
>
> --noah
>
