| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2021-02-23 | epee: return HTTP error 400 (Bad request) on deserialization error | moneromooo-monero | 1 | -2/+14 | |
| It's better than 404 (Not found) | |||||
| 2020-10-10 | Change epee binary output from std::stringstream to byte_stream | Lee Clagett | 1 | -1/+3 | |
| 2020-07-30 | epee: guard against exceptions in RPC handlers | moneromooo-monero | 1 | -9/+31 | |
| 2019-11-15 | epee: set application/json MIME type on json errors | moneromooo-monero | 1 | -0/+2 | |
| 2019-06-16 | Bans for RPC connections | Howard Chu | 1 | -2/+2 | |
| Make bans control RPC sessions too. And auto-ban some bad requests. Drops HTTP connections whenever response code is 500. | |||||
| 2019-01-28 | rpc: fix internal daemon calls in restricted rpc getting partial data | moneromooo-monero | 1 | -6/+6 | |
| 2018-12-23 | epee: better network buffer data structure | moneromooo-monero | 1 | -1/+1 | |
| avoids pointless allocs and memcpy | |||||
| 2018-11-05 | epee: log HTTP/RPC calls at info level | moneromooo-monero | 1 | -1/+6 | |
| It's useful info to have when investigating logs | |||||
| 2018-07-25 | epee: set jsonrpc to "2.0" in parse error return data | moneromooo-monero | 1 | -0/+1 | |
| 2017-11-03 | Fix file permission issue | Tim L | 1 | -0/+0 | |
| This branch fixes a file permission issue introduced by https://github.com/monero-project/monero/commit/69c37200aa87f100f731e755bdca7a0dc6ae820a | |||||
| 2017-10-30 | RPC Add cross origin resource sharing support | Tim L | 1 | -0/+0 | |
| 2017-05-27 | abstracted nework addresses | moneromooo-monero | 1 | -1/+1 | |
| All code which was using ip and port now uses a new IPv4 object, subclass of a new network_address class. This will allow easy addition of I2P addresses later (and also IPv6, etc). Both old style and new style peer lists are now sent in the P2P protocol, which is inefficient but allows peers using both codebases to talk to each other. This will be removed in the future. No other subclasses than IPv4 exist yet. | |||||
| 2017-01-16 | Change logging to easylogging++ | moneromooo-monero | 1 | -3/+6 | |
| This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. | |||||
| 2016-05-14 | Don't allow 'flush_txpool' and 'setbans' JSON_RPC methods when running in ↵ | osensei | 1 | -2/+4 | |
| restricted mode. | |||||
| 2015-11-27 | core_rpc_server: add a --restricted-rpc option | moneromooo-monero | 1 | -2/+4 | |
| It does not expose the RPC for commands like start_mining, etc (ie, commands a public node operator might want to be restricted) | |||||
| 2015-03-27 | Restore daemon interactive mode | Thomas Winget | 1 | -4/+4 | |
| Daemon interactive mode is now working again. RPC mapped calls in daemon and wallet have both had connection_context removed as an argument as that argument was not being used anywhere. | |||||
| 2014-07-25 | move modified epee code to new classes, revert license | fluffypony | 1 | -25/+22 | |
| 2014-07-23 | License updated to BSD 3-clause | fluffypony | 1 | -22/+25 | |
| 2014-05-25 | 0.8.8update | mydesktop | 1 | -95/+4 | |
| 2014-04-07 | Improvements in JSON RPC | Antonio Juarez | 1 | -47/+39 | |
| 2014-04-02 | json rpc for wallet and bugfix | Antonio Juarez | 1 | -17/+85 | |
| 2014-03-20 | some fixes | Antonio Juarez | 1 | -23/+23 | |
| 2014-03-03 | moved all stuff to github | Antonio Juarez | 1 | -0/+260 | |
 |
index : monero.git | |
| Monero: the secure, private, untraceable cryptocurrency |
| aboutsummaryrefslogtreecommitdiff |