Skip to main content

Replies sorted oldest to newest

It is real weird. I can sign in here, but not to my snipes. I have some comming up and I can not get to them. Sam said it was the cookies, but I did not change anything from when I snipped the items the other day. I was in and out and sideways with not one bit of problems. Now, I am up the creek without a paddle. I checked the cookies and nothing has been changed from before, etc.. It is real strange.
How would cookies stop you logging on? (as suggested by Sam). If your PC has access to the internet then it's either something their end (doubtful as no-one else had the problem) or something your end such as CAPS lock, a typo etc.

This isn't me having a go at you, it's me having a rant about support people who mislead users about cookies and how they work. I think there are still people out there (you know who you are!) who delete them at the earliest opportunity 'cos they're the devil's spawn. They're not - here's some info about cookies from Microsoft! And here's some more...


R2
Actually a mal-formed cookie *could* prevent you from 'automatically' logging into an area, and if set to auto expire then the problem could 'just go away on it's own'. In most cases you should still be able to log into whatever site via their normal log in facility - even if you have (or in some cases, are) a 'bad cookie'.

R2 - here's a scenario:

Member 'joe' uses his browser to log into his favorite site 'widget.com'. Widget.com loads and immediately checks for a cookie to see if the user has been there before - if not (cookie doesn't exist), it displays a log-in dialog. If they have been there before, the site validates the user-id stored in the cookie against it's member database.

Say the cookie has a little glitch, and somehow the user-id changed from 'joe' to 'jof'. Jof doesn't exist as a user on widget.com. If the people that coded the site don't handle this error properly (ie display a dialog to the user telling them they can't be found in the member database and asking them to log in), then the scenario described by Shopping could definitely be encountered. Deleting the cookie, or waiting for it to expire would clear up the problem.

Cookies may not be the devil's spawn - but poorly written cookie implementaions are Smile
R2 -

No. Cookies are stored on the users computer, not the hosts (that's why so many web sites use cookies - they don't have to keep track of all that data on their end, they just have to read (and write) the cookie from the users computer when they visit. Saves a ton of data storage for the web host). If only one user had a 'glitch' then everyone else would be fine. If the 'glitch' was on the computer hosting the web site, then everyone would probably be affected.

In any case, if the user's cookie says they're 'jof' and there isn't such a user on the website, the site should ignore the cookie and allow them to login (which would [should] reset the cookie with the correct user name).

If Shopping's problem was cookie related then I'd suggest that AS needs to recode the way they're dealing with cookies.

The reason some people think that cookies are 'the devil's spawn' is that some web sites use cookies to keep track of where you go within their site, how many times you visit, etc., then sell that information to those nasty marketing people Smile If you had to sign up on their web page then they've got a pretty good idea of who you are (email address) and what things you like (pages you've visited) - and even where you were right before you came to their site. Marketers have wet dreams about that kind of detail!

Personally, the convenience of not having to log into every site I've signed up at is worth the spam I get (I have 3 spam filters in place, so out of my normal 1000 spam emails a day, only 30 get through).
quote:
And, since Shop didn't have to delete ANY, then it doesn't appear to be sound advice.


Cookies can be (and usually are) set to expire after a certain amount of time. One wouldn't have to do anything other than wait. That's why some sites 'remember' you when you re-visit them a day later, but not a week later.

Ok. Cookie 101 is now over. Please turn in your assignments as you leave for your next class.
BJ - AS doesn't write code for an individual user - it writes codes for everyone - my point was that, if there was a problem with their code then more than one user would feel the effects.
Cookies have had a bad press in the past and, as a result, we get 'delete them all', 'turn them off' when a little TLC is all they need! Wink

R2
R2 -

You are misreading my posts, and yes, if there was a problem with AS's code it would probably affect everyone.

[caps for emphasis, not shouting] ...

BUT. If YOUR computer did something to YOUR INDIVIDUAL cookie (which is NOT stored on AS, but rather on YOUR computer), it could cause YOU and ONLY YOU problems, depending on the way AS handles errors.

The reason support monkeys tell you to delete all your cookies is that it's much easier to explain how to do that than to tell you how to find the individual cookie for their site and remove only that one.
Dave / JD - I have a chocolate chip cookie recipe that I won a contest from Better Homes & Gardens with ...

Use the 'toll house' recipe from the back of the chip package, but double the amount of chips (1/2 semi sweet & 1/2 chocolate mint), double the amount of nuts, add about 1/4 cup of chocolate mint liqueur (I can never spell that word). Place them 6 to a cookie sheet (a small handful of dough each), reduce the temperature listed on the package by 25 to 50 degrees and cook them approximately twice as long.

They come out HUGE and nice and soft.

And with a little espresso ice cream ... Smile

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×