Any Nominet EPP gurus?

monaghan · Feb 3, 2010

I'm re-writing my billing system so need to provide a full EPP client rather than the current stripped down to the minimum catch EPP code.

I'm trying to code a contact update and generating the following

Code:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <command>
    <update>
      <contact:update xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-2.0" xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-contact-2.0 nom-contact-2.0.xsd">
        <contact:roid>C121441</contact:roid>
        <contact:name>Alex Monaghan</contact:name>
        <contact:email>[email protected]</contact:email>
        <contact:phone>012345123456</contact:phone>
        <contact:mobile>01234567</contact:mobile>
      </contact:update>
    </update>
    <clTRID>MCL-00002</clTRID>
  </command>
</epp>

It returns

Code:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
  <response>
    <result code="2001">
      <msg>
        Command syntax error
      </msg>
    </result>
    <trID>
      <svTRID>190063</svTRID>
    </trID>
  </response>
</epp>

If I send each of the name, email, phone or mobile updates on its own it is accepted.

The EPP Update page at Nominet shows

<contact:update> element
The <contact:update> element contains the following child elements:

* A <contact:roid> element to contain the identifier of the contact object to be modified.
* <contact:name>
* <contacthone>
* <contact:mobile>
* <contact:email>

I'm assuming it is therefore legal to send multiple field updates.

Any suggestions or do I need to wait until tomorrow and fire a support request to Nominet?

monaghan · Feb 3, 2010

Thanks,

I was PM'd with a suggestion to change the order of the elements, this works. I also seem to recall another issue that was resolved by changing the order of the elements.

I guess Nominet must parse the EPP requests line by line requiring strict ordering rather than the more usual flexible xml processing I've used on other API's.