Closed
Bug 854131
Opened 11 years ago
Closed 11 years ago
Wrong cached port number substituted into HTTP request
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: chalx, Unassigned)
Details
I used a router web interface at http://192.168.0.1:8022. When I opened "192.168.0.1" the browser jumps to 192.168.0.1:8022 automatically (don't know was it http redirect or not). Then I've started to use another router at http://192.168.0.1. But I can't open it's web interface because browser drops me to 192.168.0.1:8022 (which is not online): GET / HTTP/1.1 Host: 192.168.0.1:8022 I've tried to open "192.168.0.1:80" but this port is transparently ignored for all http URLs. Maybe web server on 80 port is down too but I can't see it while URI switches to :8022.
Comment 2•11 years ago
|
||
Clear your disk cache and try it again.
Cache entry information key: http://192.168.0.1/ fetch count: 24 last fetched: 2013-03-23 23:46:27 last modified: 2013-03-23 19:43:07 expires: No expiration time Data size: 0 file on disk: C:\Documents and Settings\Any-admin\Local Settings\Application Data\Mozilla\SeaMonkey\Profiles\502cimm9.default\Cache\6\34\CDD70d01 Security: This document does not have any security info associated with it. Client: HTTP request-method: GET response-head: HTTP/1.1 301 Moved Location: http://192.168.0.1:8022 I believe deleting this entry will help. But it is a workaround anyway, not a solution. BTW I don't agree to clear all my disk cache any time some host will poison it...
Comment 4•11 years ago
|
||
What solution do you expect ? There is no bug as far as I can see.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•