What browser are you using when this happens? It sounds strange but there is something problematic with IE when accessing apache 2.4.2 I came across it but it happened much quicker and affected the browser on the local PC so this might not be the same issue. I wrote a blog post on it and how to upgrade to apache 2.4.3 which fixes that bug: [
astutelogic.com]