Skip to content
Tests

Fix potential CSRF circumvention with custom HTTP methods #124

Sign in to view logs

Fix potential CSRF circumvention with custom HTTP methods

Fix potential CSRF circumvention with custom HTTP methods #124

Triggered via pull request July 22, 2024 16:16
@MarkusBauerMarkusBauer
synchronize #76
MarkusBauer:fix-csrf-issue
Status Failure
Total duration 5m 9s
Artifacts –

tests.yml

on: pull_request
Matrix: linux-tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
linux-tests (8.0, sqlite)
Process completed with exit code 1.
linux-tests (8.0, sqlite)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linux-tests (8.0, pgsql)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linux-tests (8.0, mysql)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linux-tests (8.1, mysql)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/