Closed
Bug 775890
Opened 12 years ago
Closed 12 years ago
Detect non-200 responses for resources in manifests
Categories
(Marketplace Graveyard :: Validation, enhancement, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cvan, Unassigned)
References
Details
We could probably start flagging or rejecting apps whose manifests contain invalid paths/URLs.
Fields that should probably absolutely be valid paths:
- launch_path (which defaults to origin)
- icons.128 (whose path defaults to origin but could point somewhere external)
- appcache_path (if specified)
If specified, these should also be valid paths (but probably don't matter too much):
- icons.*.url
- developer.url
- locales.*.developer.url
Reporter | ||
Updated•12 years ago
|
OS: Mac OS X → All
Comment 1•12 years ago
|
||
In addition to checking the path is valid we should make sure useful content is there if it doesn't take too long. I'm duping that bug to this one.
Comment 3•12 years ago
|
||
Merged:
https://github.com/mozilla/app-validator/commit/6a94fdcc28c9501b5170a771582bed997ccc9d0a
In response to comment #1:
We do enforce a standard HTTP timeout. If this is too long, it can be reduced going forward.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•