@seji Make sure you note down and inform them of the CF Ray ID that should show on all error pages. This will help them track down where the problem lies.

I get the following from CountryTraceRoute to that IP:

1 192.168.0.1 router.asus.com Reserved 0 ms 0 ms 0 ms 0 ms 64 2 185.1.55.18 ae6.no-323-rt1.get.n Norway 19 ms 1 ms 1 ms 7 ms 252 3 185.1.55.41 Norway 8 ms 2 ms 1 ms 4 ms 251 4 104.21.90.93 United States 1 ms 1 ms 1 ms 1 ms 60

Something must be up with the routing from your ISP.

@Gwen-Dragon I think the main lesson learned here should be that developers should never rely on the HTTP referer header for anything else than just basic statistics on where traffic is coming from and to keep tab of internal broken links.

One would think that in an internal web application all requests should be same-origin anyway, but of course if they use different hosts/ports or even change between http/https they have a problem.

I am however not of the opinion that developers and operators should constantly monitor the w3c and browser spec processes, not everyone has the time to do that. They should simply try not to use stuff for purposes they were never intended to be used for, so it doesn't break down the line. KISS.

The same problem in Windows.