Re: Warn people who have perlmonks in a URL?

If anything, it's a bug in the way perlmonks is implemented. Apparently, the cookie sent is dependent on the server requested. It might be better to always send a cookie for the domain instead.

In other words, you're saying that they *can* share the cookie. If that is the case, I think it would be better to have them do so, than to try to train users to deal with the fact that they don't. (Yeah, I know, I'm not the poor admin who has to implement all these crazy demands the users have...)

I suspect it is an attempt to be friendly to clients that don't handle redirects transparently (or at all.)

The standard way to deal with that is to send, along with the refresh/redirect, a small page containing a link. But I suspect very few users would ever see the link, because all the major graphical browsers can handle refresh since about 1995, and people who use Lynx generally have been around on the net for a little while and probably aren't going to be trying to use a .com TLD to access a site like perlmonks, unless they're either fooling around or testing the site. (I'm assuming here that in addition to an HTTP refresh header you also include an http-equiv refresh in the <head> section of the document. With doing both those things, browser support is near universal.) I'm trying to imagine a Lynx user who would think of perlmonks and immediately guess, "It's probably a commerce site." A surreal notion. But if you include the link in the response along with the refresh, you cover even this edge case.

$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}}
split//,".rekcah lreP rehtona tsuJ";$\=$ ;->();print$/
[download]

Comment on Re: Warn people who have perlmonks in a URL? Select or Download Code

Replies are listed 'Best First'.
Re^2: Warn people who have perlmonks in a URL? (cookies!) by tye (Sage) on Nov 09, 2003 at 04:55 UTC
No, I don't want www.perlmonks.org and perlmonks.org to share a cookie. I don't see any advantage to that. The cookie "problem" is only due to people making links with hard-coded site information and we can address that source of the problem so what advantage is there to also addressing the same problem in a different way that doesn't address it very well? But the real reason I don't want to do this is because being able to have multiple cookies is an advantage. Every user can justify having 3 different cookies: logged out (no cookie -- when you want to see how your node looks to the average user), logged in, and logged in using "ticker" mode so that they don't show in "Other Users" (useful when you want to read/research/whatever but aren't paying any attention to the chatterbox and so don't want others to think you are hanging out when you won't notice them trying to chat with you). Now, three cookies goes well with three domains (.org, .com, and .net). But I need more than one account (tye is not in gods because it is a bad idea to spend all day as superuser) and several other people have accounts such as thepen and im2 that are used for special purposes. Some people might share a computer and have enough trust that they share a computer login and each have permanent cookies to PerlMonks at different domains. Several people have "joke" accounts that they try to be humorous with (and now we are close to the type of "extra accounts" that are discouraged and can even get you into trouble...). So there are at least several case where having 4 (or perhaps more) cookies can be useful. I'm quite glad that I can have 6 cookies (I use 4 pretty regularly and sometimes use more). www.perlmonks.org is tye. perlmonks.org is "stealth" tye who is ignoring the chatterbox. www.perlmonks.com is tye  and perlmonks.com is "stealth" tye . www.perlmonks.net is AnonyMonk and perlmonks.net is an extra for when I need to test something that I can't test as any of the above. And this could become even more useful if we go forward with vague plans about being able to have more options in a cookie (such as limited powers or custom "user settings")... - tye	[reply]
Re: Re^2: Warn people who have perlmonks in a URL? (cookies!) by sauoq (Abbot) on Nov 09, 2003 at 05:20 UTC
With IE, you can do that without multiple domains. Just open a new IE instance (don't use ^N for a new window, that won't work.) Unfortunately, that doesn't work with all browsers. -sauoq "My two cents aren't worth a dime.";	[reply]
Re: Warn people who have perlmonks in a URL? (cookies!) by jonadab (Parson) on Nov 10, 2003 at 00:51 UTC
Is this a habbit you've developed because it so happens that the domains don't share cookies, or is it the reason that the domains don't share cookies? `$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}} split//,".rekcah lreP rehtona tsuJ";$\=$ ;->();print$/` [download]	[reply] [d/l]
Re: Re: Warn people who have perlmonks in a URL? by sauoq (Abbot) on Nov 09, 2003 at 04:34 UTC
In other words, you're saying that they can* share the cookie.* Yes, www.perlmonks.org and perlmonks.org can share a cookie. And they do, so long as you log into perlmonks.org rather than www.perlmonks.org. Similarly with the .net and .com pairs. What can't be done is sharing cookies across domains. There are a number of reasons the spec doesn't allow for that, security not least among them. -sauoq "My two cents aren't worth a dime.";	[reply]