Closed Bug 721875 Opened 14 years ago Closed 13 years ago

URL extension on manifest shouldn't be required

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P1)

Product:
addons.mozilla.org Graveyard
Component:
Public Pages
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: ianbicking, Assigned: kumar)

References

Details

There's no real reason to require .json or .webapp in the manifest URL. The content-type of the resource is what really matters. I'd like to suggest developers do something like this to setup a manifest: <? header('content-type: application/x-web-app-manifest+json'); ?>{...} And technically you can append some nonsense onto the URL to give it the "right" extension, but it's unnecessary.
Assignee: nobody → cvan
Priority: -- → P1
Target Milestone: --- → 6.4.4
Assignee: cvan → kumar.mcmillan
Fixed https://github.com/mozilla/zamboni/commit/2b0b1cdededacaff700c7c292c181493f504623e
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
f. I accidentally had the validator disabled while testing locally. The validator needs a patch for this. On its way...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Patched the validator: https://github.com/mozilla/amo-validator/commit/047971aa80b389ea5300d1513f7cdfe209882e01 https://github.com/mozilla/zamboni/commit/36a5eee48747ca88673dc04a01206fdb6d519ce3 This is working now.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.