Mercurial > prosody-wiki
comparison mod_register_json.wiki @ 186:673fa35f880f
Correction.
author | maranda3985@gmail.com |
---|---|
date | Tue, 12 Apr 2011 23:52:13 +0000 |
parents | 9aab3736b3ca |
children | 4a6c1e35788c |
comparison
equal
deleted
inserted
replaced
185:9aab3736b3ca | 186:673fa35f880f |
---|---|
23 The ip field is at the moment is required to be present even if unset (""), you will require to set it using the webserver's REMOTE_ADDR global (or similar) to pass the client's ip address should you want to employ throttling/blacklisting/whitelisting of requests. | 23 The ip field is at the moment is required to be present even if unset (""), you will require to set it using the webserver's REMOTE_ADDR global (or similar) to pass the client's ip address should you want to employ throttling/blacklisting/whitelisting of requests. |
24 | 24 |
25 = Usage = | 25 = Usage = |
26 | 26 |
27 Copy the module file into your prosody modules directory. | 27 Copy the module file into your prosody modules directory. |
28 Load the module in your configuration file's global section (Host "*"), that would suffice to run it. | 28 Load the module in your configuration file's global section, that would suffice to run it. |
29 | 29 |
30 Hint: pairing with mod_register_url is helpful, to allow server registrations only via your webform. | 30 Hint: pairing with mod_register_url is helpful, to allow server registrations only via your webform. |
31 | 31 |
32 Optional configuration directives: | 32 Optional configuration directives: |
33 {{{ | 33 {{{ |