Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.
Http/1.1 Service Unavailable -- what is going on here (firefox only)
I attempt to display the AOL Mail login screen (https://my.screenname.aol.com/) but I receive
"Http/1.1 Service Unavailable" in an otherwise blank screen instead.
This occurs in Firefox...this does not occur in IE (11.0.9600)...this does not occur in Google Chrome.
Alle Antworten (9)
I think that there is no such server. If I go to screenname.aol.com I get:
The connection has timed out
The server at screenname.aol.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
screenname.aol.com gets the same reaction with firefox, IE, and chrome. I think there is no such server.
Can you log in through the AOL home page and get to your mail from there?
I apologize, Tyler.
IE works when I go to screenname.aol.com. Firefox produces the "connection timeout" message.
Can you follow the steps at Websites look wrong or appear differently than they should and then restart your computer and try again?
What security software do you have installed?
If I go (instead) to https://mail.aol.com I get the http 1/1 service unavailable error.
This second (https) URL works in IE and chrome but in Firefox I must go to the http://mail.aol.com and get re-directed to the https URL.
Now I understand WHAT to do (I don't understand WHY) Thanks to many for the suggestion to go to "http" and let it re-direct. THAT works. Fixed
Hi bstan, what you are getting on https://mail.aol.com is not normal. There is a problem either with the redirect to the login page or with the site's ability to access your logged in status. If you notice redirect/cookie issues cropping up on other sites, we should review your settings.
It seems to have something to do with attempting to go to the real destination directly (via https)
Firefox complains about http:1/1 service unavailable (and blank page)
If I go to the (dont know what to call it)--"proxy page" via http and get re-directed then it works.
IE and chrome can go directly to the "real" target URL via https. Firefox only works if I go to the "http" page and get re-directed.
I call this "fixed"--not understood but FIXED