Bug 98267
| Summary: | Failure to log-in to Windows Live ID | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | ronald.gold |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, lforschler |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1292157722&rver=6.1.6206.0&wp=MBI&wreply=http:%2F%2Fmail.live.com%2Fdefault.aspx%3Frru%3Dinbox&lc=1033&id=64855&mkt=en-us&cbcxt=mai&snsc=1 | ||
ronald.gold
Unable to log into my email account at Window Live ID. I get the following eroor message:
Windows Live ID
We're unable to complete your request
Windows Live ID is experiencing technical difficulties. Please try again later.
The URL is: https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1292157722&rver=6.1.6206.0&wp=MBI&wreply=http:%2F%2Fmail.live.com%2Fdefault.aspx%3Frru%3Dinbox&lc=1033&id=64855&mkt=en-us&cbcxt=mai&snsc=1
I get an identical error using Safari or iCab. However, I have no difficulty when I use Camino 2.1.2 or Chromium.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Lucas Forschler
I just logged into live.com and hotmail using Safari 6.0.1 and it worked just fine.
Alexey Proskuryakov
Did you try contacting Microsoft? Perhaps this was a temporary technical difficulty indeed.
ronald.gold
(In reply to comment #1)
> I just logged into live.com and hotmail using Safari 6.0.1 and it worked just fine.
Does not work with Safari 5.1.7 and OSX 10.6.8.
ronald.gold
(In reply to comment #2)
> Did you try contacting Microsoft? Perhaps this was a temporary technical difficulty indeed.
Did not bother to contact Microsoft as the "temporary technical difficulty" exists only for Safari (5.1.7 in my case), Webkit, and iCab, but Camino and Chromium tested as concurrently as possible have no problems logging in.
Ahmad Saleem
Pretty sure, this would've been fixed since 2012.
So I am going to mark this as "RESOLVED WONTFIX" (never got confirmed).