The match.com site has a basic mobile site for feature phones and a fancier mobile site for touch phones. Unfortunately, Firefox OS devices get the most basic version of the site even though they are modern touch phones. The HTTP analysis below shows how the sniffing works: Firefox Android redirected to /en-us/match/mobile/android/device.html, Firefox OS not redirected Selected HTTP response headers: Response for: 'Mozilla/5.0 (Mobile; rv:18.1) Gecko/18.1 Firefox/18.1' Response Status: 200 content-length: 10089 content-type: text/html; charset=utf-8 Response for: 'Mozilla/5.0 (Android; Mobile; rv:26.0) Gecko/26.0 Firefox/26.0' Response Status: 301 content-length: 0 location: /en-us/match/mobile/android/device.html
Some contact options: Website email form - has option for Technical Issues, Mobile or Suggestions - http://www.match.com/help/help.aspx?lid=4 Twitter account - they do reply to tweets but seem to forward most concerns to support (either phone or website email) - https://twitter.com/Match Probably the best contact - Eric Sowell, Manager of Mobile Web Applications at Match.com http://www.linkedin.com/pub/eric-sowell/32/401/5b3 http://ericsowell.com/ Let's try Eric on twitter first: https://twitter.com/MozWebCompat/status/473885353259311104
Assignee: nobody → astevenson
Status: NEW → ASSIGNED
Whiteboard: [country-all][mbd][serversniff][contactready] → [country-all][mbd][serversniff][sitewait]
Response "I'll pass on the feedback. Thanks for reaching out."
You need to log in before you can comment on or make changes to this bug.