Closed Bug 843141 Opened 12 years ago Closed 11 years ago

foodily.com doesn't recognize B2G UA as mobile

Categories

(Web Compatibility :: Site Reports, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lmandel, Assigned: karlcow)

References

()

Details

(Whiteboard: [country-all] [serversniff] [sitewait])

foodily.com serves a desktop site to B2G. Bug 823364 added an UA override for this domain. The override should be removed once the domain serves mobile content to B2G. This bug tracks the evangelism for the site to recognize the B2G UA and the removal of the override at that time.
Blocks: foodily.com
Whiteboard: [uaoverride]
contacted (webform & Twitter)
Assignee: nobody → hsteen
Status: NEW → ASSIGNED
Whiteboard: [uaoverride] → [uaoverride] [country-all] [sitewait]
Whiteboard: [uaoverride] [country-all] [sitewait] → [uaoverride] [country-all][serversniff] [sitewait]
There is some backend mobile detection that modifies the page (no redirect to separate mobile site). In addition they do some responsive CSS media query work (yay!). Here are the headers of two requests that demonstrate (through the content-length difference) the backend UA sniffing: GET / HTTP/1.1 Host: www.foodily.com User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: nn-no,nn;q=0.9,no-no;q=0.8,no;q=0.6,nb-no;q=0.5,nb;q=0.4,en-us;q=0.3,en;q=0.1 Accept-Encoding: gzip, deflate DNT: 1 Cookie: __utma=264112923.1328738330.1377545519.1377545519.1377545519.1; __utmc=264112923; __utmz=264112923.1377545519.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none) Connection: keep-alive HTTP/1.1 200 OK Content-Type: text/html;charset=UTF-8 Vary: Accept-Encoding, User-Agent Server: Jetty(8.1.10.v20130312) Content-Length: 19089 Accept-Ranges: bytes Date: Mon, 26 Aug 2013 21:45:13 GMT X-Varnish: 718643231 Age: 0 Via: 1.1 varnish Connection: keep-alive ------------------------------------------------------------------ GET / HTTP/1.1 Host: www.foodily.com User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: nn-no,nn;q=0.9,no-no;q=0.8,no;q=0.6,nb-no;q=0.5,nb;q=0.4,en-us;q=0.3,en;q=0.1 Accept-Encoding: gzip, deflate DNT: 1 Cookie: __utma=264112923.1328738330.1377545519.1377545519.1377553623.2; __utmc=264112923; __utmz=264112923.1377545519.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=264112923.3.9.1377553623 Connection: keep-alive HTTP/1.1 200 OK Content-Type: text/html;charset=UTF-8 Vary: Accept-Encoding, User-Agent Server: Jetty(8.1.10.v20130312) Content-Length: 27877 Accept-Ranges: bytes Date: Mon, 26 Aug 2013 21:45:33 GMT X-Varnish: 718643903 Age: 0 Via: 1.1 varnish Connection: keep-alive ------------------------------------------------------------------
Foodily devs are very responsive and I think this will be resolved soon :)
Whiteboard: [uaoverride] [country-all][serversniff] [sitewait] → [uaoverride] [country-all] [serversniff] [sitewait]
This doesn't seem to be resolved yet. Contacted again. Getting hungry :) http://twitter.com/MozWebCompat/status/395552296144470016
So we didn't make progress on this one. Though it seems a low hanging fruit. Jeff Kimble seems one of the architects or manager? http://www.linkedin.com/in/kimblejeff And John Cramp a software engineer there http://www.linkedin.com/pub/john-cramp/45/363/262 The twitter account has not been responsive. Unfortunately.
Assignee: hsteen → kdubost
I recontacted them today with Hallvord's contacts.
sent a reminder.
See Also: → 978658
Depends on: 980191
Removing UA override keyword by bug 980191
Whiteboard: [uaoverride] [country-all] [serversniff] [sitewait] → [country-all] [serversniff] [sitewait]
This seems to be fixed.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.