Closed Bug 471816 Opened 16 years ago Closed 15 years ago

yahoo.com, yahoo.co.jp, etc. - redirect to minimal page when the UA-string contains 2009

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: phiw2, Assigned: kev)

References

()

Details

(Keywords: top100)

Attachments

(1 file)

STR:
1. download/install the latest nightly Camino/Minefield/Shiretoko/GranParadiso
2. go to http://yahoo.co.jp/
3. enjoy minimal page with a warning to 'upgrade' your browser

Change the data in the UA string to say 'Gecko/20081231xx...' instead of 'Gecko/20090101xx...' and you get the normal page.
yahoo.com has the same problem; I think we should move this to en-US and have it cover all of Yahoo's properties, if possible.

Adding some people from bug 410430 for some déjà vu ;)  Kev, are you still the person to push this at Yahoo?  Can we convince them this year to abandon the broken "year sniffing" altogether? ;)
Assignee: japanese → english-us
Component: Japanese → English US
QA Contact: japanese → english-us
Summary: yahoo.co.jp - redirect to minimal page when the UA-string contains 2009 → yahoo.com, yahoo.co.jp, etc. - redirect to minimal page when the UA-string contains 2009
Forwarding to the folks at Yahoo, and I'll definitely ask them to review (and ideally trash) this policy. That said, I'm marking my calendar for next year :)
Assigning to Kev since he's working on this, but really just so I can say wtf? Again? I *did* have my money on Yahoo though...
Assignee: english-us → kev
Seems to work now, at least on .jp and .au (.com redirects me to .au so I can't check).

Moreover, I switched my UA date to 2010 and it still worked.
(In reply to comment #4)
> Seems to work now, at least on .jp and .au (.com redirects me to .au so I can't
> check).
> 
> Moreover, I switched my UA date to 2010 and it still worked.

.jp does not work yet.


and same bug, bug 471786
OK I made a mistake, .jp indeed doesn't work. I didn't recognise the page to be the "minimal" one.

.au does work regardless of UA date *if* UA also says "Firefox". When I reset the product to "Minefield", date started to take effect and I got the minimal page (which is much more minimal that .jp's).
reproduce UA(WinXP-trunk's UA)
Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2a1pre) Gecko/20090103 Minefield/3.2a1pre

can not reproduce UA (modifiyed "general.useragent.override")
Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2a1pre) Gecko/20080103 2008 Minefield/3.2a1pre

Yahoo's UA checker is watching "2008".
Just a quick update, I heard back from the Yahoo! Front Doors team today, and they're looking into addressing the issue and pushing a fix. They're also going to see if they can change the way they do agent string checking so we don't run into this in the future.

When I hear about a fix being pushed, I'll update the ticket.
Any chance this will be fixed before 3.0.0.6 is released? Since it will have a date of 2009 in the UA.
Yahoo! will be pushing the fix on 02-Feb-2009, and will be letting us know when the QA versions are pushed for testing. Do we have a definitive list of front-pages this affects?
(In reply to comment #13)
yahoo.co.jp does _not_ work correctly (it should show the same largish multi column design as yahoo.com).
When I first upgraded to Firefox 3, the yahoo/xtra homepage did this same thing to me ( http://xtra.co.nz or http://nz.yahoo.com ) and I had to run a user agent spoofer to view the stuff. I sent in a complaint via email and I got some idiotic "you're the only person affected by this" response.

Worse, I had a friend send in a separate complaint afterwards and do you know what they got back? "Sorry, you're the only one experiencing this problem." ... Yeah, right.

So, it's amazing that anyone has managed to convince them that their site is broken and useless - my point is that once they claim to have "fix"ed it, I'd expect it to just happen again anyway. It will be fixed only when they abandon serverside agent sniffing altogether, or do it unobtrusively.
I said yahoo.co.jp worked but still had the message.  There is a heck of a lot more content on the Japan site then the regular yahoo.com.  But regardless, the message is on the site about needing to upgrade to a "newer" browser.
Yahoo.com is fine for me using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1b3pre) Gecko/20090127 Shiretoko/3.1b3pre
Yahoo.co.jp seems to be fixed.
Both yahoo.com and yahoo.co.jp now load correctly here. But others in the list in comment 13 still fail for me:

> Doesn't Work:

> http://asia.yahoo.com/
> http://th.yahoo.com/
> http://vn.yahoo.com/
> http://ph.yahoo.com/
> http://malaysia.yahoo.com/
> http://sg.yahoo.com/
> http://id.yahoo.com/
(In reply to comment #18)
> Yahoo.co.jp seems to be fixed.

...but change the UA date to 20100127 and it's broken again. So much for a "fix".
As folks have noticed, Y! Corp. pushed the changes yesterday, as has Y! JP. The remaining sites will be updated by the SE Asian team on Monday (Singapore time). While the fix currently in place is only a filter change to accept 2009 build IDs, they'll be working on changing their UA analysis in a release in the near future to remove the date-checking so we don't get to do this again.
As far as I can tell, all Y! domains now work correctly. Resolving this as fixed. Thanks to all involved.

I didn't test what happens with a 2010 UA string. That is stuff for next years bug anyway :-)

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090322 Minefield/3.6a1pre
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: