Skip to content
build-distros

[Security] Fix XSS Vulnerability where content-type header wasn't explicitly set in API requests #18342

Sign in to view logs

[Security] Fix XSS Vulnerability where content-type header wasn't explicitly set in API requests

[Security] Fix XSS Vulnerability where content-type header wasn't explicitly set in API requests #18342

Triggered via pull request November 6, 2024 23:40
@NiniOakNiniOak
opened #21930
SECVULN-8621_consul_api_validate_request_content_type
Status Cancelled
Total duration 2m 16s
Billable time 2m
Artifacts –

build-distros.yml

on: pull_request
Setup
6s
Setup
get-go-version  /  Determine Go toolchain version
7s
get-go-version / Determine Go toolchain version
check-go-mod  /  check-go-mod
27s
check-go-mod / check-go-mod
build-386
0s
build-386
build-amd64
0s
build-amd64
build-arm
0s
build-arm
build-s390x
0s
build-s390x
build-distros-success
2s
build-distros-success
Fit to window
Zoom out
Zoom in

Annotations

4 errors
build-amd64
Canceling since a higher priority waiting request for 'build-distros-SECVULN-8621_consul_api_validate_request_content_type' exists
build-386
Canceling since a higher priority waiting request for 'build-distros-SECVULN-8621_consul_api_validate_request_content_type' exists
build-arm
Canceling since a higher priority waiting request for 'build-distros-SECVULN-8621_consul_api_validate_request_content_type' exists
build-distros-success
Process completed with exit code 1.