Closed
Bug 712790
Opened 13 years ago
Closed 13 years ago
GetPersonas.com CDN permissions issues
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fligtar, Assigned: nmaul)
Details
Loading getpersonas.com doesn't have any CSS or JS. When I look at what it's asking for: http://getpersonas-cdn.mozilla.net/static/min/?g=js&r=88676 returns a 401 with "The information you requested could not be retrieved. Invalid product type."
Assignee | ||
Comment 1•13 years ago
|
||
It appears that one (or maybe more than one) of the CDNs in use for this don't currently allow "directory-level" queries. That is, there's no filename specified in that request. There hasn't been any changes to getpersonas' CDN config in over a week. Was there a push recently that just changed this behavior?
Updated•13 years ago
|
Assignee: server-ops → oremj
Updated•13 years ago
|
Assignee: oremj → nmaul
Assignee | ||
Comment 2•13 years ago
|
||
We believe the codebase did not change significantly in some time, so this has likely been broken since on or around Dec 16, which is when Highwinds was added to the CDN pool for this. Interestingly, I get a different error. Still a 401, but the text is: Directory level requests are not allowed. I believe the issue is that Highwinds is simply not allowing queries that don't have a filename in them. I will open a ticket with them to determine the scope of this problem, and why fligtar and I would get different error messages. In the meantime, Highwinds has been disabled for getpersonas. This is done in Cedexis. Dropping prio on this bug, but keeping it open as a tracking bug for this issue in general.
Severity: blocker → normal
Assignee | ||
Comment 3•13 years ago
|
||
This was a bug in Highwinds' CDN service. They have corrected it, and I've confirmed that it is working properly again. I've re-enabled them in Cedexis, and they're getting getpersonas-cdn.mozilla.net traffic again. I'm also adding this to my mental list of "things to check that a CDN does properly before turning them on"... it was rather unforeseen. Thanks for the bug report!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•