Why does ESPN display in a linear fashion?
Beginning a couple of weeks ago ESPN.com started displaying "funny" like everything is stripped out except for the words and headings. I am going to attach a screenshot so you can see as well. Once I am on another network or connect to a hotspot it works just fine. I have espn.com and espn.go.com added as Allowed plus we do not block any of the categories it falls under so I am confused. This has happened before with money.cnn.com and a few other sties but those seem to be ok now. I drove myself crazy thinking it was a problem with my laptop but I have now tested on several other PC's and the same thing is happening with them as well. This happens across IE 10/11, Firefox, & Chrome so I don't think it is a browser issue either. Any information you could provide to fix this would be very much appreciated.
Espn.jpg
-
You have domains blocked by your settings needed to render the content properly. Why do you do this and then come to here to complain? This doesn't make sense!
When visiting espn.com, at least the following domains are being queried:
espn.com
espn.go.com espn.gns.go.com
sports-ak.espn.go.com espn.go.com.edgesuite.net a200.g.akamai.net
a.espncdn.com a.espncdn.com.edgesuite.net a1589.g1.akamai.net
a1.espncdn.com a.espncdn.com.edgesuite.net a1589.g1.akamai.net
assets.espn.go.com assets.espn.go.com.edgesuite.net a1589.g.akamai.net
tredir.go.com tredir.gns.go.com
a2.espncdn.com a.espncdn.com.edgesuite.net a1589.g1.akamai.net
player.ooyala.com player-cdn.ooyala.com player-cdn.ooyala.com.gtm.ooyala.com.akadns.net
wildcard.ooyala.com.edgekey.net e1650.g.akamaiedge.net
a3.espncdn.com a.espncdn.com.edgesuite.net a1589.g1.akamai.net
streak.espn.go.com streak.espn.gns.go.com
g.espncdn.com g.espncdn.com.edgesuite.net a1249.g.akamai.netWhen visiting money.ccn.com, at least the following domains are being queried:
money.cnn.com www.money.com
z.cdn.turner.com z.cdn.turner.com.edgesuite.net a1755.g.akamai.net
i.cdn.turner.com cdn.cnn.com.c.footprint.net
i2.cdn.turner.com cdn.cnn.com.c.footprint.net
markets.money.cnn.com markets.money.cnn.wallst.com
streamer.money.cnn.com streamer.money.cnn.wallst.comNow go and check your blocked domain stats to see which ones you have blocked by your settings and why:
https://dashboard.opendns.com/stats/all/blockeddomains -
rotblitz, while I very much appreciate you taking the time to respond I do not know why you have to be so condescending in the process. I've had the exact same settings in Open Dns for over 2 years and never once experienced this issue. As of 2 weeks ago I began having issues with ESPN rendering correctly and I thought this might be a good place to see if someone had experienced the same problem. I was thinking maybe something could have be reclassified that I was overlooking. This was my first ever posting on this forum and I apologize for being such a bother but I was not complaining, just looking for guidance. After further investigation nothing you posted appeared in my blocked domains list nor did I find anything else associated with ESPN or Go.com. I am not aware of anything that has changed with my firewall or network setup that would impact ESPN but all signs are pointing away from Open DNS and towards another layer of network protection.
Hopefully this information will help someone else along the way and the other user with the same problem to eventually figure out the issue. I rarely look at the blocked domains list and that totally slipped my mind before posting so a sincere thanks for pointing out the obvious thing I forgot to check.
-
Well, according to the picture you posted, at least the domains hosting their CSS (Cascading Style Sheets) source files seem to be inaccessible. You'll have to look into the HTML source of their pages to see where they load the CSS from.
After a quick check this seems to be a.espncdn.com, so try to visit this domain to see what happens.
-
Thanks for that info. I will export the block list to search because it is quite massive and I could have missed something upon my first cursory look. I had an "Duh" moment when you mentioned in your post to check the block list to begin with. That totally slipped my mind and I appreciate your follow up response. I will update this posting once I have a chance to export and search.
-
"it is quite massive"
Is it? It shouldn't be, else your surfing experience will significantly slowed down and many things will be broken. Only a minority of sites should be blocked unless you have persistent users with addictions and other diseases in your network trying to access blocked sites again and again, i.e. as an operator of a mental institution. You seem to be doing something wrong. It really supports my initial doubts about "Why do you do this and then come to here to complain?". See now what I meant? It was not meant to be "condescending". Over-doing is supposed to cause such troubles you're facing. You really get what you configure, be ensured.
-
On the contrary I believe I am far from over-doing anything. I am going to attach a screen shot so you can see that I have a custom setup that is quite nonrestrictive. I have maybe a dozen "always block" exceptions added mostly because they have not been categorized or were not at the time of addition.
Do you honestly feel I am being "overly restrictive" and "doing something wrong" based on these settings?. I overstated in saying massive but was larger than normal because I ran for an extended range to try and isolate some other trends I have been seeing.
OpenDns settings'.jpg -
This is medium restrictive, from my subjective perspective. But if users in your network have preferences in direction of the blocked categories, a massive list of blocked domains will be the result. You will know what you're doing.
"a dozen "always block" exceptions added mostly because they have not been categorized or were not at the time of addition."
This can be dangerous, especially if they belong to CDNs. These are normally not categorized, but they host always essential content of any kind, especially from top sites. ESPN and CCN are good examples for this. Also and especially aliases (CNAMEs) may be impacted. Whatever, from your always block list I cannot see major CDN providers being blocked, but I didn't dive deeper into it.
-
BST if you login to your Open DNS then choose Dashboard and look under the Settings tab you will need to add this at the bottom of the page under the "Never Block" section.
Sorry you got a halfhearted answer previously but some people only know how to answer by being a condescending asshole.
-
Hello All,
While one may notice that a whitelisting of a website can be "working" for a long time, this doesn't mean that the site owner won't change the site's layout, resources, or design over time. This is why these sites may get "broken".
As rotblitz has advised, putting the subdomains/domains that a site refers to on an allow list in your settings will let you render your sites properly (if they've been blocked via category filtering).
A useful site in helping you determine what kind of domains a given website refers to can be found here: http://www.webpagetest.org/
-
It was kind of a rhetorical question as I was working through it and talking out loud. What would happen is that I would just click on the Login button either on the left or at the top right in their Menu area - and then nothing at all would happen. I ended up just releasing the Go.Com site from the Blocked Domains list. It just did not seem like a battle I wanted to continue to fight. If we start having issues with unsafe go.com sites (whatever they may be) then I will just re-address it at that time. It is more of a policy issue than a technical one.
The technical issue that I was observing - while go.com was on the Blocked list, but espn.go.com was on the Allowed was the site being blocked sometimes and then allowed at other times. For example, even between IE and Firefox on the same PC, one may show blocked, the other would load the page. My user confirmed this as they encountered that enough times that they finally just bookmarked straight to the page they ultimately wanted - which seemed to be working reliably. I suspect maybe at times some content that the page really wanted to load was being blocked per my settings and it just stopped there.
-
This is a very old post and I only came across it due to a similar issue I'm having. I had to simply respond to rotblitz and how much of an ASS you were being in responding to people's questions. If you don't want to respond, DON'T. What purpose did you serve in being so condescending to the person asking the question? What level of familiarity do you think they had with troubleshooting issues with OpenDNS or searching for the necessary clues to make the decision to block/unblock sites? You came off like a simple internet troll that came way too close to throwing insults at the posters mother or their own sexual preference. If interacting with people on the internet is too much for you I would suggest to unplug your network cable and disable the wireless connection and stay indoors.
Please sign in to leave a comment.
Comments
23 comments