# HG changeset patch
# User maranda3985@gmail.com
# Date 1367270251 0
# Node ID 73b078aeaf84ae2e3a703efb182bc22f2ae60c23
# Parent  980a177b8a196128649df02ecfd381a6ee0f3881
Added description of the http error codes' meaning.

diff -r 980a177b8a19 -r 73b078aeaf84 mod_register_json.wiki
--- a/mod_register_json.wiki	Mon Apr 29 21:02:29 2013 +0000
+++ b/mod_register_json.wiki	Mon Apr 29 21:17:31 2013 +0000
@@ -26,6 +26,15 @@
 
 Your form implementation needs to pass *all* parameters, the auth_token is needed to prevent misuses, if the request is successfull the server will answer with status code 200 and with the body of the response containing the token which your web app can send via e-mail to the user to complete the registration.
 
+Else, it will reply with the following http error codes:
+
+ * 400 - if there's an error syntax;
+ * 401 - whenever an username is already pending registration or the auth token supplied is invalid;
+ * 403 - whenever registration is forbidden (blacklist, filtered mail etc.);
+ * 406 - if the username supplied fails nodeprepping;
+ * 409 - if the user already exists, or an user is associated already with the supplied e-mail;
+ * 503 - whenever a request is throttled.
+
 The module for now stores a hash of the user's mail address to help slow down duplicated registrations.
 
 It's strongly encouraged to have the web server communicate with the servlet via https.