User tests: Successful: Unsuccessful:
listen event onAfterDispatch
to keep track of API requests on actionlogs
make some requests GET for example:
/api/index.php/v1/plugins
/api/index.php/v1/users
/api/index.php/v1/config/application
/api/index.php/v1/content/article
....
etc...
test other verbs as welll
API requests logged
something like
N/A
maybe
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Language & Strings Libraries Front End Plugins |
Labels |
Added:
?
?
|
Category | Administration Language & Strings Libraries Front End Plugins | ⇒ | Administration Language & Strings Front End Plugins |
yes again
there is no need for a new event onAfterDispatch
does already the job
Looks good to me. Just needs some tests
Please fix conflicts.
Labels |
Added:
Conflicting Files
|
conflict solved
User admin performed a GET on index.php/v1/modules/site?language=%2A&state=0
*
is displayed as %2A
Labels |
Removed:
Conflicting Files
|
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-12 19:35:43 |
Closed_By | ⇒ | alikon | |
Labels |
Added:
?
|
Status | Closed | ⇒ | New |
Closed_Date | 2020-02-12 19:35:43 | ⇒ | |
Closed_By | alikon | ⇒ |
Status | New | ⇒ | Pending |
I have tested this item
Having thought about this I think we probably want to have an additional flag for this API setting. Because in the case you have mobile apps using the API actively you're going to end up having too many entries in action logs. But you might well still want other actions logged in the component.
I have tested this item
Labels |
Removed:
?
|
I have tested this item
GET: ok
POST: ok
DELETE: ok
PUT: not tested (if someone have an example I try it)
PATCH: non listed in "Verds to log" ( I test this example: https://docs.joomla.org/J4.x:Joomla_Core_APIs#Update_Article)
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-24 11:38:27 |
Closed_By | ⇒ | wilsonge |
Thanks!
thanks folks + thanks to covid19 for lockdown
Does this REALLY need a new event? Couldn’t
onAfterDispatch
work just as well here? You’d just need to check context if using that event.