Open Bug 880607 Opened 12 years ago Updated 1 year ago

When restoring pages, Firefox changes the port number of the page

Categories

(Firefox :: Session Restore, defect)

Product:
Firefox
Component:
Session Restore
Version:
21 Branch
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
REOPENED

People

(Reporter: tech, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release) Build ID: 20130511120803 Steps to reproduce: I use very much Webmin to configure my Linux boxes. either from Linux as from Windows Often, I close Firefox with one ore more tabs opened on a webmin session. Actual results: When restarting Firefox after a stop, in the tabs where there was a webmin session opened, the port 10000 used by default by Webmin is changed with another number like 10002 10005 preventing the page to load as the port is wrong. Expected results: When restarting Firefox after a stop with opened tabs, it should open not only the same urls, but also the same ports.
This may be a networking problem, but moving to Session Restore for further triage.
Component: Untriaged → Session Restore
Is this reproducible? Can you provide a few steps?
Flags: needinfo?(tech)
(In reply to Tim Taubert [:ttaubert] from comment #2) > Is this reproducible? Can you provide a few steps? Hello, it reproduce every day, as I always have many different webmin sessions opened when I close Firefox. The next day when I reopen firefox asking to restore the previous session, the urls are good but the port number are changed as I explained in my first post.
Flags: needinfo?(tech)
Can you try if this issue still exists if you run Firefox in safe-mode? With all add-ons disabled? I can't reproduce this on my machine. This might be a problem caused by one of your add-ons maybe.
(In reply to Tim Taubert [:ttaubert] from comment #4) Hello, Yesterday my firefox was automatically upgraded to release 23. I closed it with 6 webmin sessions opened and today all tab were restored with the correct url and port. It seems that this bug has been corrected in this release.
Hmm. I see three sessionstore bugs fixed in the Firefox 23 time frame but none of them would certainly change something about ports in URLs. Let's set this to WFM for now and please reopen the bug should you see it again.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Even while I'm now using Firefox 23.0.1 the problem occured once again this morning. It seems that the bug isn't corrected
I think we need a solid STR to reproduce this. We can't do anything about that until we know where that issue is coming from.
Status: RESOLVED → REOPENED
Ever confirmed: true
Keywords: qawanted
Resolution: WORKSFORME → ---
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I was unable to reproduce this on Firefox 21 (build ID: 20130511120803) and on Firefox 25 (build ID: 2013111260018). I have installed and started Webmin but the port remained 10000 (the default one) after closing and opening firefox. I've selected the option to "Show my windows and tabs from last time" to test this. Also, I've simulated several crashes using the crashme addon and the port remained unchanged. Can you please check to see if this still reproduces for you on the latest release? Thank you!
Flags: needinfo?(tech)
Hello, I had stopped reporting on this bug, but nearly every day I get this error. This morning once again I had one tab with a webmin session trying to open with port 10003 instead of 10000. I'm using the last release Firefox 25.01 under Linux Debian.
Flags: needinfo?(tech)
This morning, one of my tabs tried to open on https://localhost:10027/net/list_routes.cgi
Removing qawanted since QA can't reproduce this issue (see comment 10).
Keywords: qawanted
Two years later, this bug is still there. It seems that no body wants to take it in charge. Every day I get the same kind of error, always linked to numeric datas in the url. Everyday my webmin sessions start with a port number lightly different from the good one, and the websites accessed by their ip fail because one number of the ip is changed.
It would be helpful if, instead of complaining, you could help to find solid steps to reproduce this in a fresh profile, without add-ons. Our QA team and I have failed sofar trying to reproduce this. We would be more than happy to fix this once we find the cause.
Like every day my webmin tabs were opened with a wrong port. Today the port 10035 instead of 10000. Now I use Firefox 42 and nothing changes about this old bug.
(In reply to tech from comment #15) > Like every day my webmin tabs were opened with a wrong port. Today the port > 10035 instead of 10000. > Now I use Firefox 42 and nothing changes about this old bug. Can you explain us exactly what you do? Do you have any add-ons installed? Does this happen every time you reopen Firefox, or once in a while?
Flags: needinfo?(tech)
No actionable data from the reporter. Closing this one out.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 9 years ago
Resolution: --- → INCOMPLETE
Still have this bug, every time Firefox reopen Webmin tabs the port number is changed from 10000 to random ports starting with 10 : 10015, 10006... I still don't understand why firefox doesn't open strictly the url that was closed.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Severity: normal → S3

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.

Flags: needinfo?(tech)
You need to log in before you can comment on or make changes to this bug.