Closed
Bug 693085
Opened 13 years ago
Closed 10 months ago
Dubai Airport WLAN does not connect with Firefox
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mikko, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20100101 Firefox/6.0 Build ID: 20110811165603 Steps to reproduce: Tried to connect Dubai Airport WLAN in Terminal 1 (hotspot called maxspot). Free access, seem to be generally availalble in the terminal. Actual results: The ad page redirect during the first redirect did not complete. The connection was interrupted The connection to www.dubaiairport.com:8090 was interrupted while the page was loading. Expected results: You'll get redirected to the advertisement page https://dubaiairport.com/maxspot/index.html Tested with Firefox 6 and FF mobile 10 nightly. Neither did work. After the initial connection was made with Mobile Safari or Google Chrome Firefox could surf web pages perfectly. Only the initial redirect fails in tested FF versions.
Reporter | ||
Comment 1•13 years ago
|
||
Ooops... the browser which initiated mobile connection succesfully was stock Android browser, not Mobile Safari. Mobile Safari works too, though.
Comment 2•13 years ago
|
||
Can you provide a Mozilla http log https://developer.mozilla.org/en/HTTP_Logging ? There is not much we could do unless someone provides a ticket to dubai :-)
Reporter | ||
Comment 3•13 years ago
|
||
I am going to Dubai again in December/January. I can hopefully check then. I was secretly hoping that Mozillla foundation would sponsor a trip to its hardworking test personnel!
Updated•2 years ago
|
Severity: normal → S3
Comment hidden (spam) |
Comment hidden (spam) |
Comment hidden (spam) |
Updated•10 months ago
|
Severity: S3 → --
Component: General → Networking
Product: Firefox → Core
Comment 7•10 months ago
|
||
I'll close this as INCOMPLETE since we didn't get the http log we need.
Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•