in reply to Re: Is anyone at perlmonks aware that...
in thread Is anyone at perlmonks aware that...

My guess is that your browser(s) was caching the one (intermittently) bad IP at that time (while lwp-request was using one of the other two IPs). If you had managed to run lwp-request against the bad IP during the time of its badness, I think you would have gotten zero bytes of content in response (perhaps not even HTTP headers).

Apache can be configured such that getting "Host: 216.92.34.251" produces different results than getting "Host: perlmonks.org", but that isn't currently the case on any of the IPs currently assigned to the PerlMonks DNS names.

- tye        

  • Comment on Re^2: Is anyone at perlmonks aware that... (browser vs lwp-request)

Replies are listed 'Best First'.
Re^3: Is anyone at perlmonks aware that... (browser vs lwp-request)
by BrowserUk (Patriarch) on Jun 02, 2011 at 19:24 UTC

    Sorry, but that doesn;t seem to be the case.

    When I just read your post (accessed vis http://209.197.123.153/), I opened a new tab and typed "perlmonks.org" into Opera and again I got a blank page that competes immediately.

    I then typed:

    lwp-request http://perlmonks.org/

    [download]

    And got the front page.

    I then returned to the tab I opened and hit F5 which in Opera forces a full refresh and got another blank page.

    Finally, I fired up Firefox and went intooptions/privacy/empty recent history. Then I tried perlmonks.org and got a blank page.

    This is not a spurious problem limited to me or just one browser, nor a transient one. It cannot be so easily dismissed.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]

      I think the best approach is to leave DNS completely out of the picture.

      Currently, http://216.92.2.139/~perl2 http://216.92.34.251/index.pl (which is also accessible via sending the appropriate Host: header and accessing the IP address directly) serves a blank page for me, most likely because the cached frontpage has been generated empty.

[reply]
[d/l]

        My ignorance of web servers means I don't understand most of that.

        I can say that the link also renders a blank page which view source displays empty.

        But then, if I give that url to lwp-request it also comes up empty, so whether than is useful information I have no idea.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

      You don't appear to have understood most of what I wrote as I wasn't dismissing the complaint and your reproduction steps had really nothing to do with what I was pointing out.

      My point: lwp-request is choosing to use a different IP than your browsers are using when given the same host name. (I'm a little surprised that your browsers are so insistent on using the same IP, but that may just be a Windows thing.)

      [ But the fact that only "/" is constantly failing (on that IP) was something that I only clued into after re-reading ikegami's reply (in part due to a large number of "oh, now it is working" replies here and via other media).

      (Update: Ah, it appears that there are two different problems just on that one IP. One is "/" (the Monastery Gates) being blank (always, for everybody) and the other is lots of pages being blank only every so often (at least for some people -- perhaps based on the user's IP address). And this second probably should now be fixed, thanks to Corion. ) ]

      - tye        

[reply]

In Section Perl Monks Discussion