Regarding the XML HTTPS interface, specifically 'action => renew'.

'currentexpirationyear' is a required argument.  I may have missed
something, but it appears the only way I can programmatically retrieve
that value is via a get cookie request, then parsing the year from the
value.

    <item key="object">COOKIE</item>
    <item key="attributes">
     <dt_assoc>
      [...]
-->   <item key="expiredate">2006-02-27 20:29:24</item>
     </dt_assoc>
    </item>
    <item key="response_text">Command Successful</item>
    [...]

In some cases, the XML return data doesn't have this information present
- such as today, when renewing a domain that was expiring tomorrow.  Not
sure why the data wasn't present when the domain hadn't expired yet.

Why force the current exp year to be a required argument here?  OpenSRS
already has this information on their end of things... it seems rather
arbitrary to require it from the client.

Thanks for any insight provided.

--
Mahlon E. Smith
[EMAIL PROTECTED] / www.martini.nu
jabber: [EMAIL PROTECTED]
_______________________________________________
domains-dev mailing list
domains-dev@discuss.tucows.com
http://discuss.tucows.com/mailman/listinfo/domains-dev

Reply via email to