https://find.stage.mozaws.net/favicon.ico Failed to load resource: the server responded with a status of 401 (Unauthorized)
If you went directly to /favicon.ico, you probably just saw the vague message:
Server error
Also looks like I get occasional 503 (Service Unavailable) messages from stage (but I'm also not able to connect to my device, for unknown reasons). Here's the full-er log:
2015-04-16 14:37:09.534 0b579d96.almond.js:1 ws:opening
2015-04-16 14:37:09.535 0b579d96.almond.js:1 device:44385662405082af803f083ad5a1d2fd:command:sent {"t":{"d":60}}
2015-04-16 14:37:09.634 https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd Failed to load resource: the server responded with a status of 503 (Service Unavailable)
2015-04-16 14:37:09.666 https://find.stage.mozaws.net/favicon.ico Failed to load resource: the server responded with a status of 401 (Unauthorized)
2015-04-16 14:37:09.763 0b579d96.almond.js:1 ws:open
2015-04-16 14:37:09.826 https://find.stage.mozaws.net/favicon.ico Failed to load resource: the server responded with a status of 401 (Unauthorized)
2015-04-16 14:38:10.741 0b579d96.almond.js:1 device:44385662405082af803f083ad5a1d2fd:command:sent {"t":{"d":60}}
2015-04-16 14:38:10.844 0b579d96.almond.js:1 PUT https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd 503 (Service Unavailable)h.ajaxTransport.send @ 0b579d96.almond.js:1h.extend.ajax @ 0b579d96.almond.js:1t.Model.extend.sendCommand @ 0b579d96.almond.js:1r.extend.sendTrackCommand @ 0b579d96.almond.js:1
2015-04-16 14:38:10.845 0b579d96.almond.js:1 XHR finished loading: PUT "https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd".h.ajaxTransport.send @ 0b579d96.almond.js:1h.extend.ajax @ 0b579d96.almond.js:1t.Model.extend.sendCommand @ 0b579d96.almond.js:1r.extend.sendTrackCommand @ 0b579d96.almond.js:1
2015-04-16 14:39:11.945 0b579d96.almond.js:1 device:44385662405082af803f083ad5a1d2fd:command:sent {"t":{"d":60}}
2015-04-16 14:39:12.055 0b579d96.almond.js:1 PUT https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd 503 (Service Unavailable)h.ajaxTransport.send @ 0b579d96.almond.js:1h.extend.ajax @ 0b579d96.almond.js:1t.Model.extend.sendCommand @ 0b579d96.almond.js:1r.extend.sendTrackCommand @ 0b579d96.almond.js:1
2015-04-16 14:39:12.056 0b579d96.almond.js:1 XHR finished loading: PUT "https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd".h.ajaxTransport.send @ 0b579d96.almond.js:1h.extend.ajax @ 0b579d96.almond.js:1t.Model.extend.sendCommand @ 0b579d96.almond.js:1r.extend.sendTrackCommand @ 0b579d96.almond.js:1
2015-04-16 14:40:12.778 0b579d96.almond.js:1 device:44385662405082af803f083ad5a1d2fd:command:sent {"t":{"d":60}}
2015-04-16 14:40:12.883 0b579d96.almond.js:1 PUT https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd 503 (Service Unavailable)h.ajaxTransport.send @ 0b579d96.almond.js:1h.extend.ajax @ 0b579d96.almond.js:1t.Model.extend.sendCommand @ 0b579d96.almond.js:1r.extend.sendTrackCommand @ 0b579d96.almond.js:1
2015-04-16 14:40:12.884 0b579d96.almond.js:1 XHR finished loading: PUT "https://find.stage.mozaws.net/1/queue/44385662405082af803f083ad5a1d2fd".
Expected results:
No 401s.
Not sure if I'm just extra stupid today, or if I'm missing something, but I don't see where we actually define a favicon in the HTML/Go markup. I was initially curious why I was seeing the 401 on the signed in state, but not on the regular olde find.firefox.com homepage. I'm guessing the browser just requests that route by default, but that still wouldnt explain why I don't see the console error in all routes.
Steps to reproduce:
Actual results:
If you went directly to /favicon.ico, you probably just saw the vague message:
Also looks like I get occasional
503 (Service Unavailable)
messages from stage (but I'm also not able to connect to my device, for unknown reasons). Here's the full-er log:Expected results:
No 401s.
Not sure if I'm just extra stupid today, or if I'm missing something, but I don't see where we actually define a favicon in the HTML/Go markup. I was initially curious why I was seeing the 401 on the signed in state, but not on the regular olde find.firefox.com homepage. I'm guessing the browser just requests that route by default, but that still wouldnt explain why I don't see the console error in all routes.