in reply to perlmonks cookies

I just used the livehttpheaders extension for Firefox to see for myself. Guess what - the browser did make a request for www.perlmonks.org, and did send my www.perlmonks.org cookie.

But I don't think it's a Firefox bug (at least on 1.0), and here's why - my browser was requesting a specific page. I use Aristotle's Perl-blue theme (with a few modifications of my own) and my stylesheet link in user settings was http://www.perlmonks.org/index.pl?node_id=167905&displaytype=displaycode As soon as I took out the "www", the only cookie sent was my perlmonks.org cookie.

Replies are listed 'Best First'.
Re^2: perlmonks cookies
by ysth (Canon) on Dec 02, 2004 at 06:52 UTC
    I don't have any theme set or anything else I can guess would be hitting www.perlmonks.org all the time. I installed livehttpheaders and now can't get the problem to manifest :(

    Update: (Note: this is Firefox 1.0 on windows) I get this to happen consistently by entering a perlmonks.org address while not connected (which pops up a Windows "Choose a network connection" dialog box), connecting via a different (non-gui) process, hitting escape on the connection dialog. Then Firefox (while leaving the http://perlmonks.org... in the location field) actually fetches http://www.perlmonks.org....

    That is to say, just blame Firefox.

      From your description I would guess at a sequence of events like this:
      1. Firefox tries to find perlmonks.org and kicks open the network connection dialog.
      2. Network connection dialog blocks Firefox's attempt to resolve perlmonks.org until it is dismissed.
      3. Network connection is established outside of the Firefox/network connection dialog
      4. Canceling the connection dialog returns a failed status on the attempt to resolve perlmonks.org
      5. Firefox thinking it can't find perlmonks.org begins searching for similar names by prepending 'www.' or appending '.com', '.org', '.net', etc.
      6. Firefox finds www.perlmonks.org since there is now a valid network connection (but fails to update the URL in the location bar?)
      I would think 6 (and possibly 4) could be considered Firefox bugs and should be reported.

      That is a most impresive bug description! I hope you are going to log it to Bugzilla *grin*

      --
      Do not seek to follow in the footsteps of the wise. Seek what they sought. -Basho