Cliff Woolley
Central Systems Software Administrator
Washington and Lee University
http://www.wlu.edu/~jwoolley/
 
Work: (540) 463-8089
Pager: (540) 462-2303>>> [EMAIL PROTECTED] 05/30/00 10:51AM >>>
>It hangs a lot, especially on page reloads.  Sometimes it delivers
>pages perfectly, other times it takes half a minute.  The other day the
>error log piled up with several dozen segfault child expirations while
>checking it from a coworkers desk, which probably explains the empty
>document pages he kept getting.  I have no real clue why.
Check your SSLRandomSeed and SSLSessionCache settings.  Your SSLRandomSeed might be set to a blocking source of entropy (such as /dev/random as opposed to /dev/urandom on some platforms).  You might be using a DBM Session Cache and be using a broken DBM library.  What are these set to for you?

>The one thing amiss I can find is probably just ignorance on my part.
>When I telnet to the server, it's return output includes numbers that I
>am not seeing in my web pages, which are no logical part of the output
>that I understand, and aren't there from the normal server.
>GET / HTTP/1.1                    (** I send request headers **)
>Host: buda.bst.bls.com

>HTTP/1.1 302 Found                (** It responds correctly **)
>Date: Tue, 30 May 2000 14:39:03 GMT
>Server: Apache/1.3.12 (Unix) mod_perl/1.23 mod_ssl/2.6.4 OpenSSL/0.9.5a
>Location: https://buda.bst.bls.com:8443/
>Transfer-Encoding: chunked
 
NOTE THIS HEADER.

>Content-Type: text/html; charset=iso-8859-1

>15a                               (** but what is this? **)
><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
><HTML><HEAD>
><TITLE>302 Found</TITLE>
></HEAD><BODY>
><H1>Found</H1>
>The document has moved <A
>HREF="https://buda.bst.bls.com:8443/">here</A>.<P>
><HR>
><ADDRESS>Apache/1.3.12 Server at <A
>HREF="mailto:[EMAIL PROTECTED]
>m">bos04111.al.bst.bls.com</A> Port 8080</ADDRESS>
></BODY></HTML>
>
>0                                 (** and this? **)
The "extra" numbers denote the beginning and end of a chunk in the chunked encoding of the body of the response.  (Transfer-Encoding: chunked).  If you had a long response, it could be in multiple chunks.  That's all.  So no, they're not part of the web page, and yes, they are correct.  =-)  This is completely unrelated to slowness/hangs/segfaults.
 
Hope this helps.
 
--Cliff

Reply via email to