Closed
Bug 187725
Opened 23 years ago
Closed 23 years ago
Microsoft Online Crash Analysis Blocks Mozilla from Status Page
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 187408
People
(Reporter: mysterioususer, Assigned: susiew)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
When attempting to view the status of a crash report (doesn't matter which one,
just click on "Status" in the left side link), Microsoft hands out a list of
requirements that you need to meet before you can view it. They recommend
either Netscape 6+ or IE5+. However, when viewing in either Phoenix or Mozilla
1.2.1 on XP, Microsoft brings up this requirements page, which I presume means
they don't like the browser I'm using. Using Netscape 7.01 to view the Status
page works fine. You do not need to have a passport or a crash report to view
in order to see this bug in action. Perhaps Microsoft is checking for a literal
"Netscape" string?
Reproducible: Always
Steps to Reproduce:
1. Go to http://oca.microsoft.com/
2. Click on "Status" link on the left side
3. Watch MS throw back page that says "To track the status of an error report,
you must be running Internet Explorer 5 or later or Netscape version 6 or later,
and you must have a valid Microsoft Passport."
Expected Results:
Using Netscape 7.01, I get a passport login screen. I didn't attempt this on IE
(I assume Netscape 7 was performing the right behavior)
One more thing: using uabar on phoenix 0.5 and setting it to Netscape 7.0 UA
works just fine for accessing the site, so MS might actually be checking
specifically for Netscape.
Comment 2•23 years ago
|
||
dupe
*** This bug has been marked as a duplicate of 187408 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•