Obsolete
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Digging around a bit, it appears WebKit itself doesn't handle authentication at all.
Instead, it would appear on Android that the package org.apache.http.auth does this.
Instead, it would appear on Android that the package org.apache.http.auth does this.
gb...@google.com <gb...@google.com> #3
It's definitely not passing through the information. Here's a snippet from my Apache
log:
---
192.168.10.199 - - [20/Nov/2008:20:14:37 -0600] "GET /file.txt HTTP/1.1" 401 401 "-"
"AndroidDownloadManager"
log:
---
192.168.10.199 - - [20/Nov/2008:20:14:37 -0600] "GET /file.txt HTTP/1.1" 401 401 "-"
"AndroidDownloadManager"
al...@google.com <al...@google.com> #5
Any update on this issue?
rr...@google.com <rr...@google.com> #6
Apparently there isn't anything else to say concerning this is there.
Description
Alert Details
Description: A build failed athttps://ci.chromium.org/ui/p/chromeos/builders/staging/staging-chromiumos-sdk-pupr-generator
name: ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator
current value: 1
threshold: Gt(0) for 3m
alert fields: {, metric:builder=staging-chromiumos-sdk-pupr-generator,metric:bucket=luci.chromeos.staging}
sent at: 2025-02-11 10:42:32
active since: 2025-02-11 10:41:07 (1 min 25 secs)
If this alert is caused by an outage that affects our Gerrit usershttps://chopsdash.appspot.com to let our users know that
in chromium-review or chrome-internal-review, remember to create a
ChOps Announcement at
we're aware and working on the issue.
Useful Links
playbook:https://g3doc.corp.google.com/company/teams/chrome/ops/chromeos/chromeos-infra/build/oncall/alerts/ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator.md
console: auto/cloud:chromeos-bot
logs:https://pantheon.corp.google.com/logs/query;query=;timeRange=2025-02-11T18:42:32Z%2F2025-02-11T18:42:32Z--PT1H?project= http://alertmanager.corp.google.com/#view=createSilence&query=_monarch_mdb_role%3D%22chromeos-build-monitoring%22,alertname%3D%22ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator%22,conditionname%3D%22ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator%22,monarch_metric_fields%3D%22metric%5C:builder%5C%3Dstaging%5C-chromiumos%5C-sdk%5C-pupr%5C-generator%5C,metric%5C:bucket%5C%3Dluci%5C.chromeos%5C.staging%22,monarch_module_name%3D%22staging-chromeos-build-alerts%22,monarch_target_fields%3D%22%5E%24%22,monitorname%3D%22monarch%22,service%3D%22staging-chromeos-build%22 http://mac.corp.google.com/incident/3116938882818506788 http://mac.corp.google.com/condition?filter=service:staging-chromeos-build+label_exact:alertname:ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator+label_exact:conditionname:ChromeOSStagingBuildbucketBuildFailureChromiumOSSDKPUprGenerator+label_exact:_monarch_mdb_role:chromeos-build-monitoring+label_exact:monitorname:monarch+label_exact:monarch_module_name:staging-chromeos-build-alerts+label_regex:monarch_metric_fields:%22metric%5C:builder%5C%3Dstaging%5C-chromiumos%5C-sdk%5C-pupr%5C-generator%5C,metric%5C:bucket%5C%3Dluci%5C.chromeos%5C.staging%22+-has_label:monarch_target_fields+is:active
silence:
incident:
conditions:
Query
graph (at the triggered): link link
graph now: