843160 - ehow.com doesn't recognize B2G UA as mobile

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Lawrence Mandel [:lmandel] (use needinfo)]

ehow.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.

Comment 1

[Joshua Smith [:joshua-s]]

I am contacting eHow.

Comment 2

[Hallvord R. M. Steen [:hallvors]]

Be careful when testing, eHow sets cookies that send you to a certain version based on earlier UA strings..

I find however that not every nook and corner of the mobile version works. If you go to "slideshow"-type articles they are paged-by-swiping, but swiping doesn't work for me :-( Now tracked as bug 907674.

Comment 3

[Hallvord R. M. Steen [:hallvors]]

(Sorry Karl, didn't intend to "needinfo" you after all..)

Comment 4

[Hallvord R. M. Steen [:hallvors]]

http://www.ehowhelp.com/anonymous_requests/new might be a contact point, BTW

Comment 5

[Karl Dubost💡 :karlcow]

This is still receiving the desktop site. 
Giving background for people of ehow.

Firefox OS User Agent is:
User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0


# Firefox OS

GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: www.ehow.com
User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0

HTTP/1.1 200 OK
Cache-Control: max-age=2807
Connection: keep-alive
Content-Encoding: gzip
Content-Length: 9622
Content-Type: text/html
Date: Thu, 03 Oct 2013 15:15:13 GMT
ETag: "c5277333121dde7969da59df32738f9b:1376074226"
Server: Apache
Set-Cookie: dmp=desktop:default; expires=Thu, 10 Oct 2013 15:15:13 GMT; path=/;
Vary: Accept-Encoding


# Firefox for Android
GET / HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, compress
Host: www.ehow.com
User-Agent: Mozilla/5.0 (Android; Mobile; rv:18.0) Gecko/18.0 Firefox/18.0

HTTP/1.1 200 OK
Cache-Control: max-age=477
Connection: keep-alive
Content-Encoding: gzip
Content-Length: 3170
Content-Type: text/html
Date: Thu, 03 Oct 2013 15:15:40 GMT
ETag: "c5277333121dde7969da59df32738f9b:1376074226"
Server: Apache
Set-Cookie: dmp=mobile:default; expires=Thu, 10 Oct 2013 15:15:40 GMT; path=/;
Vary: Accept-Encoding

Comment 6

[Karl Dubost💡 :karlcow]

Contacted again using http://www.ehowhelp.com/anonymous_requests/new

Comment 7

[Karl Dubost💡 :karlcow]

I sent them again a batch of issues. 

I also noticed that their Press section has not been updated since 2011. Dead site?
http://www.ehow.com/ehow-press-kit.html
The blog is still active
http://www.ehow.com/blog/


Digging a bit more. The site ehow belongs to Demand Media
http://www.demandmedia.com/

One of their offices is just at the corner.
http://www.demandmedia.com/contact-us/

Comment 8

[Karl Dubost💡 :karlcow]

Pointed DemandMedia to http://arewecompatibleyet.com/#list:custom:ehow.com
through twitter http://twitter.com/MozWebCompat/status/406094988649725952

Comment 9

[Karl Dubost💡 :karlcow]

So. About 3 months later, the support desk of ehow replied with a status. 

> Thanks for sending this feedback.
> 
> We automatically forwarded your message to the Content Review team.
> 
> The review process can take several weeks to complete. 
> Content deemed inappropriate will be removed. 
> Additions will be made at the discretion of our content experts. 
> If you feel your feedback hasn't been addressed within the next 
> few weeks, reply to this message to escalate your concern.
> 
> In the meantime, this request will be marked "Solved" and closed.

So they marked it solved on their board. I hoped it will not get lost in the process. Content Review Team doesn't seem to be the appropriate team for it.

Comment 10

[Karl Dubost💡 :karlcow]

A designer working for ehow 
http://www.miimfoo.com/about.html
http://mimifukada.com/portfolio-item/ehow/

I sent a message to her.

Comment 11

[Karl Dubost💡 :karlcow]

Trying to contact another human working at Demand Media
http://twitter.com/MozWebCompat/status/514295952606113792

Comment 12

[Hallvord R. M. Steen [:hallvors]]

Attachment: Screenshot from Flame smartphone

Comment 13

[Karl Dubost💡 :karlcow]

This is fixed.

Comment 14

[Karl Dubost💡 :karlcow]

rha not solved. My mistake. There are very persistent cookies. It means that once you have accessed with a type of devices it stays in that mode even if you change the UA.

Comment 15

[Karl Dubost💡 :karlcow]

This is fixed. I tried on both desktop with firefox OS UA and on Firefox OS device.