PANDI · REFERENSI PENGEMBANG EPP
Kode respons EPP
Response EPP memakai kode numerik pada <result>. Kode respons membedakan transaksi berhasil, tertunda, dan ditolak.
EPP responses use numeric <result> codes. Result codes distinguish successful, pending, and rejected operations.
Cara kerja
Response EPP memakai kode numerik pada <result>. Kode respons membedakan transaksi berhasil, tertunda, dan ditolak.
- 1000: perintah selesai; 1001: diterima tetapi penyelesaian tertunda.
- 2003/2004/2005: parameter atau format tidak tepat.
- 2101/2105: perintah tidak didukung atau objek tidak memenuhi syarat.
- 2200–2305: otorisasi, relasi, status, atau objek tidak ditemukan.
Kode yang muncul dalam hasil uji atau protokol terkait
| Code | Makna | Penanganan |
|---|---|---|
1000 | Command completed successfully | Perintah berhasil |
1001 | Command completed successfully; action pending | Diterima; masih pending |
1300 | Command completed successfully; no messages | Poll queue kosong |
1301 | Command completed successfully; ack to dequeue | Poll message harus di-ack |
1500 | Command completed successfully; ending session | Logout berhasil |
2003 | Required parameter missing | Parameter wajib tidak ada |
2004 | Parameter value range error | Nilai parameter di luar batas |
2005 | Parameter value syntax error | Sintaks parameter salah |
2101 | Unimplemented command | Perintah tidak didukung |
2105 | Object is not eligible for renewal | Objek tidak memenuhi syarat renew |
2200 | Authentication error | Autentikasi gagal |
2201 | Authorization error | Tidak berhak mengakses objek |
2202 | Invalid authorization information | AuthInfo tidak valid |
2301 | Object pending transfer | Objek dalam proses transfer |
2302 | Object exists | Objek sudah terdaftar |
2303 | Object does not exist | Objek tidak ditemukan |
2304 | Object status prohibits operation | Status melarang operasi |
2305 | Object association prohibits operation | Relasi objek melarang operasi |
2306 | Parameter value policy error | Parameter melanggar kebijakan |
How it works
EPP responses use numeric <result> codes. Result codes distinguish successful, pending, and rejected operations.
- 1000: completed; 1001: accepted but pending completion.
- 2003/2004/2005: invalid parameters or syntax.
- 2101/2105: unsupported command or invalid eligibility.
- 2200–2305: authorization, association, status, or missing object.
Codes found in tests or the underlying protocol
| Code | Meaning | Handling |
|---|---|---|
1000 | Command completed successfully | Command successful |
1001 | Command completed successfully; action pending | Accepted; still pending |
1300 | Command completed successfully; no messages | Poll queue empty |
1301 | Command completed successfully; ack to dequeue | Poll message awaits acknowledgement |
1500 | Command completed successfully; ending session | Logout succeeded |
2003 | Required parameter missing | Required parameter missing |
2004 | Parameter value range error | Parameter out of range |
2005 | Parameter value syntax error | Invalid parameter syntax |
2101 | Unimplemented command | Unsupported command |
2105 | Object is not eligible for renewal | Not eligible for renewal |
2200 | Authentication error | Authentication failure |
2201 | Authorization error | Unauthorized object access |
2202 | Invalid authorization information | Invalid authorization information |
2301 | Object pending transfer | Object pending transfer |
2302 | Object exists | Object exists |
2303 | Object does not exist | Object missing |
2304 | Object status prohibits operation | Object status prohibits operation |
2305 | Object association prohibits operation | Object association prohibits operation |
2306 | Parameter value policy error | Parameter policy violation |
Permintaan dan respons XML
Contoh XML bersifat ilustratif, menggunakan identitas dan domain contoh. Jangan kirim nilainya ke server produksi.
XML permintaan
XML · Permintaan
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0">
<command>
<info><domain:info><domain:name>missing-example.id</domain:name></domain:info></info>
<clTRID>REG-EXAMPLE-0001</clTRID>
</command>
</epp>XML respons
XML · Respons
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0">
<response>
<result code="2303"><msg>Object does not exist</msg></result>
<trID><clTRID>REG-EXAMPLE-0001</clTRID><svTRID>SERVER-EXAMPLE-0001</svTRID></trID>
</response>
</epp>