Closed
Bug 299482
(update404)
Opened 19 years ago
Closed 19 years ago
Check fro updates show error "AUS: Update XML File Not Found (404)"
Categories
(Toolkit :: Application Update, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: junkmail1, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702 Firefox/1.0+ Issue may be caused by http://www.mozilla.org/update/ as going to this URL shows 403: Access Forbidden You don't have permission to access: /update/ Reproducible: Always Steps to Reproduce: 1. Select update from firefox 2. 3. Actual Results: AUS: Update XML File Not Found (404)
Comment 1•19 years ago
|
||
This is probably a dupe of bug 299482 Both are probably invalid as the new update service has not been enabled yet.
Comment 2•19 years ago
|
||
That's right, the feature is atm experimental and you need to change the internal URL to get this working.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Alias: update404
Comment 10•19 years ago
|
||
FYI: From bug 300903: If you want to use it with Deer Park Alpha 2, enter the following value for app.update.url in about:config: https://aus-staging.mozilla.org:8711/update2/0/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/update.xml Once the update feature is officially enabled, will those testers who have made the above setting need to remember to [do what]? BTW: Typo in the Summary: fro --> for
Comment 11•19 years ago
|
||
> Once the update feature is officially enabled, will those testers who have made
> the above setting need to remember to [do what]?
No worries. We have a migration plan in place that does not require anyone to
change their prefs.
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•