Closed
Bug 152114
Opened 22 years ago
Closed 20 years ago
msn.co.jp - Mozilla Denied access server-side
Categories
(Tech Evangelism Graveyard :: Japanese, defect, P1)
Tech Evangelism Graveyard
Japanese
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: hendikins, Unassigned)
References
()
Details
(Whiteboard: deny)
Tested 1.0 on Windows and Linux. Attempting to access http://www.msn.co.jp gives a "Download IE" page. Using UA Bar to spoff useragent and selecting IE6/WinXP works.
Reporter | ||
Updated•22 years ago
|
Whiteboard: deny
% curl -I http://www.msn.co.jp HTTP/1.1 403 Access Forbidden Server: Microsoft-IIS/5.0 Date: Wed, 16 Apr 2003 10:08:22 GMT Connection: close Content-Type: text/html Content-Length: 172 <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href='http://notices.msn.co.jp/upgrade.asp?t=http://www.msn.co.jp/home.armx'>here</a>.</h2> </body></html>
Blocks: MS
Priority: -- → P1
Hardware: PC → All
Summary: Mozilla 1.0 Denied access to MSN Japan → msn.co.jp - Mozilla Denied access server-side
Comment 2•21 years ago
|
||
Changing component and QA.
Component: Asian → Japanese
QA Contact: ruixu → gashu
Now MSN Japan (http://www.msn.co.jp/) is accessible with Mozilla. Confirmed with 1.4rc2 on Windows.
Comment 4•21 years ago
|
||
MSN still let users click on msn.co.jp/home/aspx, should we mark this fixed or wfm or leave it open for the remaining initial warning ?
Comment 6•20 years ago
|
||
If we disable cookie, we are redirected to the warning page. But if we enable cookie, and once we check a checkbox in the bottom of the page, then we can go directly to the top page. I recommend WFM.
Comment 7•20 years ago
|
||
Marking WFM, I guess MSN will always try to recommend IE or MSN anyway, we can't probably tell them to do otherwise.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
here's no accesibility issue, even MS recommends IE. VERIFIED.
Status: RESOLVED → VERIFIED
Updated•9 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
•