On 21 November 2014 15:03, Piers Rowan <piers.rowan@recruitonline.com.au> wrote:
On 21/11/14 13:56, Brian May wrote:
The first random thought that enters my head is maybe the visitors are using an ISP that has some sort of transparent proxy that is filtering requests to port 80.
No idea if this will explain it or not, just a thought.
Thanks Brian,
From speaking to the clients and them following up with their ISP's the claim that there is no proxying going on.
They say that, but if it works differently on port 6000 to port 80, then it sounds awfully likely that there IS something different about the path the traffic takes. Change your web server to support SSL*and then see if the clients who are having trouble can access the SSL version without the same trouble. (As the secured version has to be pass-thrued by transparent proxies or otherwise the cert won't match) -Toby * you can get free SSL certs these days; StartSSL was easy enough for me to use, but there are probably others.