Allowed HTML - you can use: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

463 thoughts on “And in next week’s Guardian, Joseph Goebells reviews Mein Kampf.

1 14 15 16
  • Clark

    Those who tend towards conspiratorial explanations of world events are likely to be disappointed by most of the StateLog material. Looking for “bad men” is like looking for the particular water vapour molecules that cause stormy weather.

  • Anonymous

    “”” at November 29, 2010 2:24 AM; thanks, but that still doesn’t answer my question”

    It does. What’s missing is “”, the name of the site.

    See for how it works behind one well-known server. I agree it’s a diversion, but I’m just passing through.

  • Clark

    Tell me where I’m going wrong. The initiating browser makes the DNS request. A DNS server replies with the IP address (and some other information?). The browser then uses the IP address to request the page directly from the target web server.

    So if that’s right, how does the browser combine the IP address from the DNS server with the remaining required information in the URL?

    We have three parties here; the browser, the DNS server (I know, there is a cascade of these; treat them as one if possible), and the target web server. Please be specific about which is speaking to which at each stage.

  • Anonymous

    Clark –

    1) the browser contacts a webserver at an IP address. The site name resolves to that address, that’s where the DNS comes in.

    2) The content the browser requests from that server is specified by the URL. That specification probably includes the site name, so that they can run a whole bunch of sites out of the same server by giving each of them a different name (all of which resolve to the same IP address, of course, or the server never has to deal with requests for them at all because they don’t get there).

    3) Try installing a server on your own machine and playing around with it. It’s not hard to do, and you’ll get the idea pretty quickly with a bit of trial and error.

  • Clark

    Thanks for trying to answer my question, but I’m looking for more specific information. I think you’ve provided a rough sketch, but the details are filled in (for you) by technical knowledge which I lack, and wish to acquire.

  • Anonymous

    Clark – Hence my point 3). I acquired these details by working out how to make it happen.

    If you write site names into /etc/hosts, they get resolved without needing to hit DNS, so you can set yourself up a bunch of names that point at localhost. Then set up a server on localhost to supply something for them when asked (of course, your port 80 is already firewalled against incoming …). Any linux will give you a choice of very-easily-installed servers. apache is (arguably) over-complicated, but at least it’s copiously documented. lighttpd is much simpler but pehaps needs a little more of a “coder” mentality to write a config for. HTH.

  • Mister pikavippi

    I give birth to be familiar with a scarcely any of the articles on your website at this very moment, and I definitely like your line of blogging. I added it to my favorites web period list and last will and testament be checking assist soon. Please check out my put as highly and leave to me conscious what you think. Thanks.

  • Suhayl Saadi

    Ha! I like it, whoever posted that at 7:14pm. Well, perhaps not a chicken. Insufficiently upper-class. Perhaps a pheasant, or a grouse… or a turkey?

1 14 15 16

Comments are closed.