Closed
Bug 1201877
Opened 11 years ago
Closed 11 years ago
Extensions download paths need an Etag and CORS
Categories
(Cloud Services :: Operations: Marketplace, task)
Cloud Services
Operations: Marketplace
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mat, Assigned: jason)
Details
We have the following in our marketplace.conf:
location <%= netapp_root %>/shared_storage/signed_apps/ {
internal;
add_header Etag $upstream_http_etag;
add_header Access-Control-Allow-Origin $upstream_http_access_control_allow_origin;
alias <%= netapp_root %>/shared_storage/signed_apps/;
}
The same thing - particularly the Etag and Access-Control-Allow-Origin bits - are needed for extensions, both signed and unsigned (we don't have reviewer-signed extensions yet, at the moment we let reviewers download an unsigned file instead). The paths we currently use should be <%= netapp_root %>/files/extensions-signed and <%= netapp_root %>/files/extensions , I think.
| Reporter | ||
Comment 1•11 years ago
|
||
Note: https://bugzilla.mozilla.org/show_bug.cgi?id=1201888, which should land this week, change the path to <%= netapp_root %>/shared_storage/signed-extensions/ and <%= netapp_root %>/shared_storage/extensions/. So please use those paths instead of the ones from comment 0.
| Assignee | ||
Comment 2•11 years ago
|
||
Added to nginx config:
https://github.com/mozilla-services/svcops-puppet/commit/99d1382cb4958339558760a49dc67e8591414ec8
https://github.com/mozilla-services/puppet-config/commit/0ccbdfa0de05454bf7f505a8bd075801c59e93d2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•