🚀 go-pugleaf

In article <364fafa2$0$12764@nntp1.ba.best.com>,
Derek Beda  <beda@shell11.ba.best.com> wrote:
>Recently I had some complaints from users that sometimes when they view
>a page on my site, not all of the graphics load correctly.  I now have
>seen this for the first time.  Some of these graphics have been online
>for a long time, I just added new ones to the page, but both new and old
>show the problem.  Is this something on the best server?

I expect this is an instance of our nagging random error where a
page will just come back blank.  No one has managed to nail down why
this happens, but I got some of my pages like this today.

In article <72ocg2$2ah$1@machaut.medieval.org>, mccomb@medieval.org (Todd Michel McComb) wrote:

>I expect this is an instance of our nagging random error where a
>page will just come back blank.  No one has managed to nail down why
>this happens, but I got some of my pages like this today.

Yeah, I'm still seeing this 2 or 3 times a week. It always seem to
fix itself within a minute or so which makes followup difficult.
It also suggests, to me at least, that it's cache-related - I mean
the caching within the httpd (not the browser). I've never been able
to catch it redhanded with telnet 80 but I'm almost certain the
server drops the connection before sending any headers.

-- 
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Malcolm Hoar           "The more I practice, the luckier I get". |
| malch@malch.com                                     Gary Player. |
| http://www.malch.com/               Shpx gur PQN.                |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In article <365014a7$0$12762@nntp1.ba.best.com>,
Malcolm Hoar <malch@malch.com> wrote:
>Yeah, I'm still seeing this 2 or 3 times a week. It always seem to
>fix itself within a minute or so which makes followup difficult.
>It also suggests, to me at least, that it's cache-related - I mean
>the caching within the httpd (not the browser). I've never been able
>to catch it redhanded with telnet 80 but I'm almost certain the
>server drops the connection before sending any headers.

bestwwwd automatically kills its listening processes after a finite
period of time to prevent any problems from building up... it's been
suggested that this problems occurs when the process about to serve
the page is killed before it does so, and then presumably that the
result is cached.

malch@malch.com (Malcolm Hoar) writes:

>In article <72ocg2$2ah$1@machaut.medieval.org>, mccomb@medieval.org (Todd Michel McComb) wrote:
>>I expect this is an instance of our nagging random error where a
>>page will just come back blank.  No one has managed to nail down why
>>this happens, but I got some of my pages like this today.

>Yeah, I'm still seeing this 2 or 3 times a week. It always seem to
>fix itself within a minute or so which makes followup difficult.
>It also suggests, to me at least, that it's cache-related - I mean
>the caching within the httpd (not the browser).

I have had this happen regularly when loading pages off line. It
loads the page or the undisplayed images after a "Back"/"Forward"
cycle. Never figured out what is preventing loading, just dealt
with it.
-- 
    B.E.Johnson             Space: To go and learn is reason enough!
    bj@imperialearth.com
    http://www.imperialearth.com/

In article <bjspace.911244512@shell3.ba.best.com>, bjspace@best.com (B.E. Johnson) wrote:

>I have had this happen regularly when loading pages off line. It
>loads the page or the undisplayed images after a "Back"/"Forward"
>cycle. Never figured out what is preventing loading, just dealt
>with it.

Methinks you are referring to a different problem. The issue
which I was describing (Todd too, unless my wires are crossed)
normally exhibits itself as a random "Document Contains No Data"
error - even on static pages. It's definitely an httpd issue.

The problem I think you are describing, is different. That's
a local caching problem with the browser. Is this Netscape?
If so, I see it too. You may find that the following trick
will help reduce the frequency of this and other Netscape
oddities.

Every day or two, I quit Netscape and physically delete the
contents of the 'cache' directory and the 'netscape.hst' file.
These appear to get corrupted from time to time and cleaning
things out seem to help quite a bit. YMMV of course ;-)

-- 
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Malcolm Hoar           "The more I practice, the luckier I get". |
| malch@malch.com                                     Gary Player. |
| http://www.malch.com/               Shpx gur PQN.                |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~