Closed Bug 329028 Opened 19 years ago Closed 19 years ago

session cookie should keep it port address value to maintain its uniqueness

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 189784

People

(Reporter: homer.yau, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.7) Gecko/20050414 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.7) Gecko/20050414 User write two separate applications on one hostname machine. e.g. access from these url: https://hostname1:4850 and https://hostname2:4851 Mozilla nor Firefox should treat these two application to be two separate session and two separate cookie on one Browser session. Current behavior is when login to first application on the first tab and then the second application on the second tab, mozilla 1.7.12 and firefox 1.5.0.1 will timeout the first application session even with two browser instance. But on two IE instance will not. Reproducible: Always Actual Results: Currently it will time out the first session. When second request come in, it will take it as a new session. Require login over and over between this two application on one mozilla browser between two tab or even two instance of Mozilla. Expected Results: Mozilla and firefox should treat those two session as two separate session since the request is going to different port and therefore it should maintian it session for as long as the application timeout. It should treat different port on the same host as individual session at all time. For an develop, if I develop multiple application on the same host using different port, I don't want to login everytime when switching between tabs or browser instance. The current workaround is to use IE Browser, since it doesn't have tab feature and it treat different port on the same host as different session.
Related to/duplicate of Core bug 189784, Core bug 142803 and bug 295396 comment 1?
With those bugs, it seems to be known issue. However, no one addressing this issue. As mention, Browser client should be able to keep mulitiple session individually if the source server are using different port address.
*** This bug has been marked as a duplicate of 189784 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.