Closed
Bug 1252626
Opened 9 years ago
Closed 9 years ago
Set up a stage Nginx proxy for the signed content
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Content Services Graveyard
Tiles: Ops
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: nanj, Assigned: relud)
References
Details
Hi relud,
Please set up a Nginx proxy server for the signed content in stage. If possible, the URL of this server could be "content.stage.mozaws.net".
There is a demo Nginx conf file here, https://github.com/oyiptong/splice/blob/master/scripts/nginx.conf#L53
Note that the bucket name needs to be updated once it's created on S3.
Via this proxy, the use should be able to get the signed content as follows,
$ curl -v http://content.stage.mozaws.net/remote-new-tab/v1/nightly/index.html
The "Content-Signature" and "Encryption-Key" will be attached in the response header, if the content was signed by Splice.
Thanks,
Nan
Thanks
| Reporter | ||
Updated•9 years ago
|
Assignee: nobody → dthorn
| Assignee | ||
Comment 1•9 years ago
|
||
this is up:
> curl -si https://s3_proxy_tiles.stage.mozaws.net/test/v1/release/en-US/index.html
| Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•