178158 - Cookie blocking ignores port number, but Cookie Manager menu doesn't.

Status: VERIFIED DUPLICATE of bug 176950

(Core :: Networking: Cookies, defect)

Description

[Christian Reis]

I found out an odd bug with cookie management and ports. I run a local
webserver, and this server listens on noth port 8000 and 80. If I browse using
port 8000, however, the cookie management seems to work a bit wierd. Here's what
I found:

a) If I am browsing at port 8000 and the server tries to store a cookie, the
popup for blocking will show up, and if I click on the "remember" checkbox and
then reject, an entry is added in the cookie sites for server kiko.kicks-ass.org
with *NO* port.

However, after this the Cookie Manager submenu will *NOT* make the "Unblock from
this site" menuitem available.

Cookies are expected rejected/accepted correctly even through the port number in
the URL does not match the host in the cookie sites tab.

b) If I am browsing at port 8000 and I use the menu to block the cookies from
the site I am browsing, an entry gets added to Cookie Manager for the site:8000.
 However, cookies from the site are *not* blocked at all, and
blocking/unblocking makes no difference.

So, in summary, the menu items seem to manipulate the manager correctly, but
cookie management seems to ignore the port number when actually doing what it
needs to (and when adding a server to the cookie sites list).

Note that NS4 shows the port number in the cookie confirmation dialog correctly
after the server name:

      The server kiko.kicks-ass.org:8000 wished [...]

Whereas Mozilla shows:

      The site kiko.kicks-ass.org wants [...]

This is nightly 20021028.

Comment 1

[Darin Fisher]

-> me

Comment 2

[Cathleen]

dup of 176950

*** This bug has been marked as a duplicate of 176950 ***

Comment 3

[benc]

v/dupe.