Skip to content

RANGER-4213: Getting 302 status code instead of 419 in case of sessio… #805

RANGER-4213: Getting 302 status code instead of 419 in case of sessio…

RANGER-4213: Getting 302 status code instead of 419 in case of sessio… #805

Triggered via push September 18, 2024 10:22
Status Failure
Total duration 26m 53s
Artifacts 2

maven.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
docker-build
Process completed with exit code 1.
docker-build
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/

Artifacts

Produced during runtime
Name Size
target-11
1.22 GB
target-8
1.22 GB