https://bz.apache.org/bugzilla/show_bug.cgi?id=61501
--- Comment #9 from Mike Lothian <m...@fireburn.co.uk> --- That seems logical, however I'm still able to go to the site that I'm proxying directly, and only a stopping and starting the apache reverse proxy fixes the issue. I'd expect a problem with the backend to show when communicating directly or at least be fixed by doing a refresh on the browser, not a restart of the apache reverse proxy I'll need to get root access of the server to try and get a tcpdump. I'll attach it when I've got that done Is there any other debugging options I can use to get more information out? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
