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
Thanks for epp-client. Supporting 40+ registries, including DENIC over RRI and EURid, in one MIT-licensed client is a lot to keep working.
I’ve built an open-source mock EPP server and a DENIC RRI one for testing clients offline. It runs as a single container with no credentials or OT&E account (docker run --rm -p 7700:7700 riftcell/epp-mock:latest), and the repo includes runnable PHP examples for both protocols (docs/examples/php/). The part I think is most useful is fault injection, which sandboxes can’t give you on demand: connection delays, login failures (always, flapping, hanging), abrupt disconnects, malformed frames, and success responses naming the wrong resource.
To be upfront: the mock is stateless, answers domain/contact/host commands with success and no response data, and doesn’t support poll. So it tests connection handling, framing and error paths, not parsing of registry responses. Repo: https://github.com/riftcell/epp-test
Would that be useful for epp-client’s CI? If so, I’d gladly add whatever responses or scenarios you’d want, for example resData for info commands. If you already cover this, I’d love to hear how.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Namingo,
Thanks for epp-client. Supporting 40+ registries, including DENIC over RRI and EURid, in one MIT-licensed client is a lot to keep working.
I’ve built an open-source mock EPP server and a DENIC RRI one for testing clients offline. It runs as a single container with no credentials or OT&E account (docker run --rm -p 7700:7700 riftcell/epp-mock:latest), and the repo includes runnable PHP examples for both protocols (docs/examples/php/). The part I think is most useful is fault injection, which sandboxes can’t give you on demand: connection delays, login failures (always, flapping, hanging), abrupt disconnects, malformed frames, and success responses naming the wrong resource.
To be upfront: the mock is stateless, answers domain/contact/host commands with success and no response data, and doesn’t support poll. So it tests connection handling, framing and error paths, not parsing of registry responses. Repo: https://github.com/riftcell/epp-test
Would that be useful for epp-client’s CI? If so, I’d gladly add whatever responses or scenarios you’d want, for example resData for info commands. If you already cover this, I’d love to hear how.
Thanks,
RiftCell
All reactions