Closed
Bug 611227
Opened 14 years ago
Closed 14 years ago
can not update a plugin through a private http url
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
INVALID
People
(Reporter: xxie, Unassigned)
Details
We build a plugin, packed as xpi, build a updateKey, signed with mccoy, using the updateKey. When I deploy the update.rdf (use the digital signature verified by the same updateKey) and the new version xpi at my personal sever, I test the find-update function in the addon windows. But it always feeds back the error information that my update.rdf did not contain a signature. I use my sever to update some personal extensions and get successful results, so I think the method of updating a plugin may be different from the method of update an extension.
Updated•14 years ago
|
Component: General → Plugin Finder Service
Product: Firefox → Toolkit
QA Contact: general → plugin.finder
Comment 1•14 years ago
|
||
It shouldn't make a difference if the XPI has a plugin or not; extensions are updated in the same way. Can you please provide a sample of the XPI you're testing with?
Component: Plugin Finder Service → Add-ons Manager
OS: Windows 7 → All
QA Contact: plugin.finder → add-ons.manager
Hardware: x86 → All
Comment 2•14 years ago
|
||
Can you please turn extensions.logging.enabled in about:config to true and check the Error Console for the exact error?
Finally I found it is just a misspelling problem, sorry for take up yours time. I'll close this bug report.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Resolution: FIXED → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•