Closed Bug 843160 Opened 9 years ago Closed 6 years ago

ehow.com doesn't recognize B2G UA as mobile

Categories

(Web Compatibility :: Mobile, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lmandel, Assigned: karlcow)

References

()

Details

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

Attachments

(1 file)

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.
Blocks: ehow.com
Whiteboard: [uaoverride]
I am contacting eHow.
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.
Assignee: nobody → hsteen
Status: NEW → ASSIGNED
Flags: needinfo?(kdubost)
(Sorry Karl, didn't intend to "needinfo" you after all..)
Depends on: 907674
Flags: needinfo?(kdubost)
Whiteboard: [uaoverride] → [uaoverride] [country-all] [sitewait] [serversniff]
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
Assignee: hsteen → nobody
Status: ASSIGNED → NEW
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/
Assignee: nobody → kdubost
Status: NEW → ASSIGNED
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.
A designer working for ehow 
http://www.miimfoo.com/about.html
http://mimifukada.com/portfolio-item/ehow/

I sent a message to her.
Blocks: 907674
No longer depends on: 907674
Trying to contact another human working at Demand Media
http://twitter.com/MozWebCompat/status/514295952606113792
This is fixed.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
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.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This is fixed. I tried on both desktop with firefox OS UA and on Firefox OS device.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.