> This may be a silly question, but has hardware been checked? I would
> start by checking: network wiring to the machine; the machine's RAM.

I don't mind silly; I'm just that desperate.  I'll do what I can to check those 
things, but given that I've seen the same results with the test server on a 
physical machine and a virtual machine, it's probably a long shot.  Both 
machines are pretty quiet, plenty of RAM, disk, and CPU.  And I wouldn't think 
a hardware issue would be resolved by moving to an https://localhost URL.

If I find something awry, I'll post.  Thanks for the suggestion.

Jim
  • svn c... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
    • ... Nico Kadel-Garcia
      • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
        • ... Daniel Sahlberg
          • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
            • ... Johan Corveleyn
              • ... Daniel Sahlberg
                • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
                • ... Nathan Hartman
                • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
        • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
          • ... Johan Corveleyn
            • ... Williams, James P. {Jim} (JSC-CD4)[KBR Wyle Services, LLC] via users
              • ... Daniel Sahlberg

Reply via email to