I am not permanently connected to the internet. When I log in to a project's website, I usually uncheck the 'Stay logged in on this computer' box - I'm afraid that I will forget to logoff, and that when I disconnect the dynamic IP address I was using might be left 'privileged' in regard to accessing that website - I figure I'd want the website to "time out" if I forget.

Lately, more and more project websites are responding 'Unable to handle request - not logged in' when I *do* perform a logout. Don't get me wrong - I'm not complaining. It just seems odd that when I explicitly request that the 'privileged' (i.e., logged in) state be ended, the site grumbles.

For a while I was curious about how many cookies were being set on various sites, so I set FF up to require me to approve/deny all cookies.

I don't know the code behind it on the BOINC project sites. But yes, at least one (if not a couple) cookies are set when you log in.

I have also seen the behavior you note where the site complains it can't complete the request when you try to log out.

I'll try to make a list tonight of the affected sites and enter it into Trac. But I've been getting side tracked lately when I start to enter bugs into Trac.

---

Kathryn :o)

mikus...

Which projects are showing this behavior?

I just went through my entire list of BOINC projects and was able to log out on all of them.

But I swear I saw what you're reporting at some point in time.

---

Kathryn :o)

Which projects are showing this behavior?

I'm quite paranoid when it comes to cookies. I use FF, and have taken the technical steps available to me to ensure that, while cookies are accepted by the browser (and kept in memory), they will __not__ get written out to disk when the browser session gets closed. Thus I do *not* keep persistent cookies.


I went through the eight projects I had attached to my "big" system, and performed a log-in followed by a log-out for each:

Four projects behaved "properly" (that is, I loggged off and stayed logged off) --
Docking, ABC, LHC, Einstein

Four projects gave me the response "Unable to handle request" --
Leiden, Malaria, QMC, Simap


Further than that, as far as I was concerned there was a bug with the websites of the four projects which told me they were unable to handle my logoff request -- When (within a reasonable period of time) I again tried to load the page for my account -- it *worked*. Meaning that when they said "unable" they meant it -- as far as those websites were concerned, I *did* remain logged in.

[When I closed my browser session and started a new one, and tried some of the four "misbehaving" websites, they required a 'new' logon. So wiping out cookies (by closing the browser session) did get rid of the "misbehaving".
.

I'm not sure what's going on. If you let me know what version of FF (I have 2.0.0.4 on Vista, XP and Ubuntu) and tell me exactly what you have set under privacy and security in options, I'll try to replicate.


While you're at it, you might want to think about opening a ticket in Trac.

---

Kathryn :o)

I'm not sure what's going on. If you let me know what version of FF (I have 2.0.0.4 on Vista, XP and Ubuntu) and tell me exactly what you have set under privacy and security in options, I'll try to replicate.

While you're at it, you might want to think about opening a ticket in Trac.

I use FF 2.0.0.4 on all the systems I have installed. Looking at the settings, none of them seem exceptional to me [if something is not mentioned, it is not checked in options]. Privacy panel: History - remember visited pages for 2 days; Cookies - accept cookies from all sites (no exceptions), and keep them until I close FF; Private Data - always clear upon close: Saved Form, Cache, Cookies, Saved Passwords, Authenticated Sessions. Security panel: Warn when sites try to install add-ons (no exceptions); Warning messages - if viewing page with low-grade encryption.


--------

In my original post I said: "Don't get me wrong - I'm not complaining." I was __not__ asking for help. My reason for posting was to alert others that they too might possibly get this kind of response to log-off. If they see it, and have complaints, let them open a ticket.


I myself question the procedure of "first ask the reporter for details about his system". [I once had a __software__ APAR rejected by IBM on the grounds that "This problem was reported on an EISA system. We do not have an EISA system on which to reproduce this !!!] To my mind, most problems worth looking at will have "replicated themselves". If a problem shows up only within a restricted environment, there might be better fish to fry.
.

2. With FF set to "delete cookies when FF closes", if I login to Malaria with "stay logged in" checked then close FF before logging out of Malaria then I am required to login again if I want to access my Malaria account 1 minute later, as it should be. Mikus, I think you are saying it does not work that way for you?

For me, too, it works the way you have described here. I had written earlier:
When I closed my browser session and started a new one, and tried some of the four "misbehaving" websites, they required a 'new' logon. So wiping out cookies (by closing the browser session) did get rid of the "misbehaving".


p.s. Two other "misbehaving" projects are Rosetta and Predictor.
.

Ah ha!

It only pops up when you uncheck the stay logged in box. I had seen it at work... That's what I was remembering.

I think it's a bug (but then again, what do I know). I'll open a Ticket for it tonight if I haven't thrown the computer across the room....

---

Kathryn :o)

BTW, before you throw a computer be sure to unplug the cables that are attached with screws, usually just the printer and monitor. If you don't then they tend to go only a short distance and then fall down on your toe :)

Ugh...

Goes to open the Trac Ticket.

Edit... done...

Ticket #304

And about throwing the computer... well that's the nice part about a laptop. Would be even better if I actually had a router. Then I wouldn't have to worry about a power cord or modem when it gets chucked across the room.

(as an aside if these linking errors when building boinc.dll don't stop, I'm gonna have a fit)

---

Kathryn :o)

before, switch to wifi and you can have a clean throw :D

LOL. Yeah. That's what I meant with my router comment. Obviously coherence isn't my strong suit these days. Must be the 9 hours a day around small children.

---

Kathryn :o)

Rytis checked in a change to fix this earlier.

I tested it out for him and it appears to work.

Changeset 13066

---

Kathryn :o)

For me it's still not working at the 4 sites Mikus mentioned, Leiden, Malaria, QMC and SIMAP. It does work at ABC and other sites but it's always worked at those sites.

Maybe those 4 sites need to update their site code.

Rytis just checked in the change last night. I tested it for him on his test page. Projects will have to update the relevent code. Best bet is to post a message at the projects asking them to update.

---

Kathryn :o)