> > as far as I remember this is just a key that prevents double renewals. > The system will renew a domain but will not renew a second try with > the same key (and also will cancel all pending orders if any with the > same key). Setting it as a current expiration year is just one way to > set a unique value. > >
So, two things: 1. That's exactly my point. The domain expires in 2008. I sent an API request to renew it 2007 to 2008 and put in 2007 as the current expiry year. According to the docs, that should mean that the data submitted does not conform to the data at the registry, triggering the error, but instead, it (without issue or complaint) renewed it to 2009, which was not my intention (especially since the invoice that went to the client showed a new expiry date of 2008 when he had already paid a renewal to 2008). 2. I guess that explains the difference between the 541 & 555 errors in that, one checks against (or is *supposed to* check against) the registry and the other checks against previous calls to the API. Either way, it didn't do its job of preventing a duplicate renewal. Incidentally, I had a bug in my code last year that sent two of everything (two calls to the API with the same data, two invoices to the customer, etc.) and I never once got any error pertaining to the double renewal of the domain names. I probably should have figured it out back then. I still say that either this should be fixed to operate the way the docs state, or the docs should be clarified with regard to these errors not actually being returned in the scenarios they present. Thanks Brian > --- _______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
