The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
{
"binaries": [
{
"binary_name": "golang-1.8",
"binary_version": "1.8.3-2ubuntu1.18.04.1"
},
{
"binary_name": "golang-1.8-go",
"binary_version": "1.8.3-2ubuntu1.18.04.1"
},
{
"binary_name": "golang-1.8-go-shared-dev",
"binary_version": "1.8.3-2ubuntu1.18.04.1"
},
{
"binary_name": "golang-1.8-src",
"binary_version": "1.8.3-2ubuntu1.18.04.1"
},
{
"binary_name": "libgolang-1.8-std1",
"binary_version": "1.8.3-2ubuntu1.18.04.1"
}
]
}{
"binaries": [
{
"binary_name": "golang-1.22",
"binary_version": "1.22.2-2~22.04.3"
},
{
"binary_name": "golang-1.22-go",
"binary_version": "1.22.2-2~22.04.3"
},
{
"binary_name": "golang-1.22-src",
"binary_version": "1.22.2-2~22.04.3"
}
],
"availability": "No subscription required"
}{
"binaries": [
{
"binary_name": "golang-1.22",
"binary_version": "1.22.2-2ubuntu0.4"
},
{
"binary_name": "golang-1.22-go",
"binary_version": "1.22.2-2ubuntu0.4"
},
{
"binary_name": "golang-1.22-src",
"binary_version": "1.22.2-2ubuntu0.4"
}
],
"availability": "No subscription required"
}