Content Delivery Paths - Places where things can go bad

There are cases where  a client or user can see something completely broken and other see it as fine.  Some typical reasons for this are:

  • Logged In vs Not Logged in.
  • Different Browser or Computer Platforms
  • Different URL  (caps vs non-cap, hyphens vs underscore ...)
  • Bad copy of a file caught somewhere along the delivery path.
The  image below addresses the delivery path.  If the problem is not in the server cache, then it is possible that a bad copy has been cached at any point after the server cache.