Doesn't respond with SERVFAIL when throwing an error #2
Chargement…
Référencer dans un nouveau ticket
Sans contenu.
Supprimer la branche "%!s(<nil>)"
La suppression d’une branche est permanente. Bien qu’une branche supprimée puisse temporairement subsister, elle NE PEUT PAS être facilement restaurée. Continuer ?
When an error is thrown (such as malformed json data that cannot be written as binary), the server should respond with SERVFAIL
Here's how to observe this error:
Create a db file with bad data (the required field "exchange" is missing from the MX record):
fail.json
Installing and running the digd.js server:
In another terminal, while the server is running:
The server throws an error and nothing comes back. Instead a SERVFAIL should come back.
Note: we should also validate the date... but we should correct the server's handling of error cases before we correct the case that causes an error.