Closed Bug 754487 Opened 13 years ago Closed 12 years ago

Check charset encoding when parsing manifest files

Categories

(Marketplace Graveyard :: Developer Pages, defect)

Product:
Marketplace Graveyard
Component:
Developer Pages
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: kumar, Assigned: kumar)

References

Details

Currently manifest files are assumed to be utf8 but MDN says they can pass in a custom charset header. We need to parse that charset header here: https://github.com/mozilla/zamboni/blob/0b43a1e4cf6fe632a956ad892518f55793ca635d/mkt/developers/tasks.py#L294
MDN docs: https://developer.mozilla.org/en/Apps/Manifest#section_4
Blocks: 752013
Priority: -- → P3
Blocks: 766201
No longer blocks: 752013
Blocks: 766199
No longer blocks: 766201
Assignee: nobody → xwraithanx
Blocks: 782711
No longer blocks: 766199
Target Milestone: --- → 2012-08-16
Target Milestone: 2012-08-16 → 2012-08-23
Target Milestone: 2012-08-23 → 2012-08-30
Assignee: xwraithanx → kumar.mcmillan
Target Milestone: 2012-08-30 → 2012-09-06
bug 788341 is more important
Priority: P3 → --
Target Milestone: 2012-09-06 → ---
Made irrelevant by bug 773871.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.