Closed
Bug 432490
Opened 17 years ago
Closed 17 years ago
safebrowsing server returning 400s frequently
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
FIXED
People
(Reporter: dcamp, Unassigned)
References
Details
(Whiteboard: [external dependency])
With the new safebrowsing server, 400s are happening on redirects quite often. I don't see a real pattern yet, but I am getting a 400 at some point in almost every initial update.
Reporter | ||
Comment 1•17 years ago
|
||
This is a server-side-only bug that we need to figure out before we can close 402469.
Flags: blocking-firefox3?
Whiteboard: [external dependency]
Updated•17 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Comment 2•17 years ago
|
||
It looks like there were two separate issues here. One was a parsing bug, the other was data replication potentially happening in an unexpected way. Both should be fixed in a new release that will be live in an hour or so. We will see if this fixes the problem.
Comment 4•17 years ago
|
||
restoring cc list
Comment 5•17 years ago
|
||
We have pushed our fix and we haven't seen any real issues with 400's since then. Dave, are you okay with closing this bug?
Reporter | ||
Comment 6•17 years ago
|
||
Yep.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
I'm seeing warning on a debug build that has been up and idle for about 18 hours.
WARNING: Didn't fetch all safebrowsing update redirects: file /Users/clint/code/fx-trunk/mozilla/toolkit/components/url-classifier/src/nsUrlClassifierStreamUpdater.cpp, line 307
The warning was thrown twice in succession, and has been quiet since. Looking through scroll-back, it seems that these are the only occurrences of it. I'll keep my eyes peeled to see if it starts happening more frequently. And if so, reopen this bug.
Reporter | ||
Comment 8•17 years ago
|
||
(fwiw, that's the error we show when a redirect fails)
Assignee | ||
Updated•10 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•