Closed Bug 226335 Opened 21 years ago Closed 21 years ago

Allow different windows/tabs to use different cookies for the same site, simultaneously

Categories

(Core :: Networking: Cookies, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 117222

People

(Reporter: rgil, Assigned: darin.moz)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030

The tabs do not keep individual session info. When using two tabs for 1 site it
says your allready logged in on the second tab. Impossible to login with
different accounts on different tabs. This is on all sites, im using windows
2000 service pack 4 build 5.00.2195 with mozilla 1.6a

Reproducible: Always

Steps to Reproduce:
1. Log into any site on one tab
2. Try logging into the same site on another tab
3.

Actual Results:  
the same login is produced on the second tab

Expected Results:  
separate session handling per tab
To networking, but the expectation is that there is a single cookie set that
applies to all currently running tabs and windows.  I'm not sure why your
expectations are different...
Assignee: general → darin
Component: Browser-General → Networking
QA Contact: general → benc
when running IE this problem does not happen. IE is however running in separate
windows but this functionality should apply to tabs as well. 
Are we talking about HTTP authentication 'login' (which I have a feeling that 
IE may handle per-window), or cookie 'login' (which I'm fairly sure IE handles 
in exactly the same way as Mozilla, i.e., globally)?
Standard web logins, not per directory server side login... cookies would depend
on the site that is being logged into and if IE handles it per window... would
it be possible for mozilla to handle it per tab?
Again, by 'standard web login', do you mean 1) The method described in the 
HTTP 'standard', where you enter credentials into the dialog box that pops up 
during HTTP authentication, before you get a page, or: 2) where you enter 
credentials into a 'login page' (like with bugzilla). 

I'm assuming you meant the first case, though the second one is used by almost 
every 'consumer' web site out there, so from that point of view it's 
the 'standard'.

Confirming as a valid RFE, changing summary and component accordingly, and 
dropping severity to 'enhancement', since this isn't a bug, per se. Note that 
this is somewhat related to bug 55181 (and it also blocks meta bug 61681).
Blocks: 61681
Severity: major → enhancement
Status: UNCONFIRMED → NEW
Component: Networking → Networking: HTTP
Ever confirmed: true
Summary: Tabbed Sessions indevidual logins → Allow different windows/tabs to use different HTTP credentials for the same site, simultaneously
yes i am referring to the consumer standard login just like bugzilla. That is my
contribution to mozilla and thanks.
So this is just another dup.

*** This bug has been marked as a duplicate of 117222 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
HTTP authentication and Session Cookies are not the same thing.  i don't think
this is a duplicate bug.

reopening... if you feel that i've misunderstood, please explain :)
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Unmorphing and re-duping. darin: I inadvertently morphed the bug in comment 5
while I was trying to clarify the bug, based on a misunderstanding about what
the reporter wanted.

*** This bug has been marked as a duplicate of 117222 ***
No longer blocks: 61681
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Component: Networking: HTTP → Cookies
Resolution: --- → DUPLICATE
Summary: Allow different windows/tabs to use different HTTP credentials for the same site, simultaneously → Allow different windows/tabs to use different cookies for the same site, simultaneously
Malcolm: ok, thanks for the clarification.  i too was fairly confused by the
original bug report ;-)

marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.