Closed
Bug 1024956
Opened 10 years ago
Closed 9 years ago
In Windows, FF will not load page at address ending .103
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ju, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140506152807
Steps to reproduce:
Attempt to load web page from local IP address ending in .103 (specifically, 192.168.1.103 in test case).
Specific FF Version 29.0.1 in Windows 7 64 Bit
Actual results:
Firefox does not display the page and remains in the "loading" state until eventual timeout.
Wireshark traces show that the page is successfully retrieved in full with no difference to "working" cases at other addresses. HTTP request completes fully.
No adblockers etc. active.
When the server IP is moved away from .103 & page loads OK we can re-enable all installed plugins and there is nothing on the page/server that is blocked - page loads correctly.
We have tried this with several different configurations:
PC1: Dual boot Windows 7 64-Bit / Ubuntu 12.04 LTS 64-Bit
Results:
In Windows the bug occurs reliably, switching the serving device to address .102 or other addresses the page loads correctly every time. Using other browsers the page loads correctly.
Booting to Ubuntu and loading Firefox (29.0) the page loads correctly from address .103 or any other.
PC2: Windows 7 32-Bit, FF 29.0.1
Results:
Bug occurs reliably, switching the serving device to address .102 or other addresses the page loads correctly every time.
PC3: Windows XP 32-Bit, FF 29.0.1
Results:
Bug occurs reliably, switching the serving device to address .102 or other addresses the page loads correctly every time. Using other browsers the page loads correctly.
PC4: Not a PC but an IP video streaming controller
Results:
Can communicate with the server at .103 and successfully execute HTTP requests to the same web server.
Pages from the server can be loaded by other devices (smartphones etc.) with no problems, whatever address we set it to.
Expected results:
Page should display!
We can provide Wireshark traces and server-side logs/debug if it would help.
Comment 2•9 years ago
|
||
Hello,
Can you please try to reproduce this issue on the latest release(43.0.4), latest Nightly(46.0a1) and provide the results?
(https://www.mozilla.org/en-US/firefox/new/)
(https://nightly.mozilla.org/)
When doing this, you could create a new clean Firefox profile, or maybe test in safe mode, as some of this issues may be caused by third party installed addons or custom settings
(https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems).
Thank you,
Vlad
Flags: needinfo?(ju)
Comment 3•9 years ago
|
||
Hi,
Considering the fact that the reporter did not provide more informations on my request, I will mark this issue as Resolved - Incomplete.
If you can still reproduce this, feel free to reopen it and provide the requested information.
Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ju)
Resolution: --- → INCOMPLETE
Apologies, I had missed the request for extra info but on briefly re-testing with version 44.0 this now seems to be resolved.
You need to log in
before you can comment on or make changes to this bug.
Description
•