List Archives constantly prompting for login

[Kathy Gee]

User is constantly being prompted to login when clicking on any link within List Archives.

[Kathy Gee (kathyg)]

This is still happening from the Admin GUI ... When a member (user) accesses the archives, everything is fine. System does not prompt for login each time a link is clicked. However, when accessing the archives from the Admin Page, system prompts for login with every link clicked.

[Kathy Gee (kathyg)]

Never mind! It working now. Must be the cache or something! Consider this bug fixed.

[Kathy Gee (kathyg)]

Upon further tests on the new Artemis system, this is still a problem and it definitely has something to do with cookies. Also, note that this problem occurs AFTER the custom changes were applied. To be specific, here are the steps performed to isolate the problem relating to cookies:

1) Accessed the archives from Admin GUI and system keeps prompting for login with every click on the page
2) Accessed the archives as a list member and system prompted for login only once (at the beginning)
3) Re-access the archives from Admin GUI and system didn't prompt for login at all (since initialy login to admin page)
4) Deleted all cookies, closed browser, repeated prompts came back when accessing archives from Admin GUI.

Robin, Jen has asked if you can please look into this?

[Terri (terriko)]

In unmodified mailman, this usually means cookies aren't turned on, but that's probably not the problem here. It is possible that the cookie being generated is somehow messed up and Mailman can't read it if there were any changes to cookies, though.

Some related FAQ entries that might help in tracking it down:

http://wiki.list.org/pages/viewpage.action?pageId=4030602

This one is related to redirection for SSL. If at some point in your test bed, the list URL was changed, this could be the problem.

http://wiki.list.org/x/moA9

This one is about cookie-related issues.

[Terri (terriko)]

Missed one: more cookie issues: http://wiki.list.org/x/loA9

[Gloria W (gloriajw)]

So how does this get resolved? Do you move the installation, or proxy everything through to the primary domain, to make it look like the same domain to the browser? Also, are cookies domain-wide, as it stands now?