Closed
Bug 1050576
Opened 10 years ago
Closed 6 years ago
[B2G][Settings][FMD] FMD page incorrectly shows find.firefox.com as the link
Categories
(Firefox OS Graveyard :: FindMyDevice, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.0 affected)
People
(Reporter: jschmitt, Unassigned)
Details
(Whiteboard: [SUMO-b2g])
Attachments
(1 file)
51.08 KB,
image/png
|
Details |
Description: find.firefox.com does not load on web browsers and the FMD page on the device says to go to find.firefox.com when only the https://find.firefox.com works. Repro Steps: 1) Update a Flame device to BuildID: 20140807000201 2) Open Settings > Firefox Accounts 3) Sign into or sign up for an account 4) Confirm the account 5) Back out to the Settings page 6) Select Find My Device and enable FMD 7) Attempt to load find.firefox.com on a desktop web browser Actual: find.firefox.com in FMD is misleading as the website needs https://find.firefox.com Expected: The FMD page to say https://find.firefox.com or the browser webpage redirects the user Environmental Variables: Device: Flame 2.0 BuildID: 20140807000201 Gaia: 8cc28fd31905a0ea2b2e15d13e80a0eab2feb1ba Gecko: 25980b5120b0 Version: 32.0 (2.0) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Notes: Repro frequency: 100% See attached: screenshot
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
Assignee: nobody → kglazko
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Comment 1•10 years ago
|
||
I also ran into this issue when configuring/testing Find My Device. It's a bit confusing - after setting up Firefox Accounts, Find My Device is listed as one of the services but there is no additional information. Going into the Find My Device submenu shows the link as described in comment 0. Thanks!! =) - Ralph
Updated•10 years ago
|
Whiteboard: [SUMO-b2g]
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]: the link needs the https:// prefix. it is a bad experience when users enter find.firefox.com in the browser url bar and not reach the landing page ni:ggp:JR is there a client side fix? if not can we handle this server side?
blocking-b2g: --- → 2.0?
Flags: needinfo?(jrconlin)
Flags: needinfo?(ggp)
Comment 3•10 years ago
|
||
On the stage boxes, i've addressed this by adding the following nginx rule: server { listen 80 default; rewrite ^ https://$server_name$request_uri permanent; } I believe that oremj may need to apply this.
Flags: needinfo?(jrconlin) → needinfo?(oremj)
Comment 4•10 years ago
|
||
Looks like there's already a bug tracking this on github: https://github.com/mozilla-services/FindMyDevice/issues/261
Comment 5•10 years ago
|
||
2.0 is closing down, very hard to get changes in. Triage recommendation is to not block, have the server side workaround be implemented, and have the client side fix ride the trains. Thanks y'all -> backlog.
blocking-b2g: 2.0? → backlog
Comment 6•10 years ago
|
||
(In reply to JR Conlin [:jrconlin,:jconlin] from comment #3) > On the stage boxes, i've addressed this by adding the following nginx rule: > > server { > listen 80 default; > rewrite ^ https://$server_name$request_uri permanent; > } > > I believe that oremj may need to apply this. Added redirect in https://github.com/mozilla-services/puppet-config/pull/793. I haven't pushed it to prod yet.
Flags: needinfo?(oremj)
Updated•10 years ago
|
Flags: needinfo?(ggp)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Updated•10 years ago
|
Assignee: katebugzilla → nobody
Component: FxA → FindMyDevice
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Comment 7•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•