You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take a look at https://github.com/ernestothorp/epp-client
If you need something else let me known.
I think they will not approve the pull request of my fork, because the didn't followed all the specs from the RFC
According to rfc5730-5732 elements below the specific command tag should have
the object type as namespace:
RFC example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <check> <obj:check xmlns:obj="urn:ietf:params:xml:ns:obj"> <obj:name>example1</obj:name> [...] </obj:check> </check> [...] </command> </epp>
Currently the domain and contact objects create xml without the
"obj" namespace. This causes xml validation errors with various registries.
According to rfc 5731 the domain check xml should look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <command> <check> <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name>example.com</domain:name> <domain:name>example.net</domain:name> [...] </domain:check> </check> <clTRID>ABC-12345</clTRID> </command> </epp>
The text was updated successfully, but these errors were encountered: