On Saturday, February 1, 2020 at 12:09:52 AM UTC-8, Paul wrote:
Robert in CA wrote:
I was expecting to find video.foxnews.com as well as
just www.foxnews.com. Whatever wraps the video (the Akamai viewer),
needs DOM storage somewhere.


I went back and checked again looking
for video.foxnews and there was another
entry for Fox or it's the same one that
came back somehow as if it's in a loop
and returns after booting?

https://postimg.cc/dkmfxpy1

I deleted it but with the same results
and I did not find a video.foxnews. I
guess I just have to live with it.

Thanks,
Robert

There are other methods, but they wouldn't be as much fun.

You could use sysinternals.com ProcMon, start collecting a
trace and see what file is accessed by the browser, when
you turn the Closed Caption in the player ON and OFF.

https://docs.microsoft.com/en-us/sys...nloads/procmon

The problem with that, is ProcMon collects a large amount
of data. You can stop data collection by unticking the tickmark
under the File menu item when you're finished and you think the
"turning ON and OFF" has been captured. But then you have to decide what
event filter makes the "most efficient" result from the trace,
such as WriteFile perhaps. Then, collect up all the resulting
stuff, save as .CSV (comma separated variable for spreadsheets),
then use some other tools to find references to foxnews.

Only occasionally when I go on a mission like that, am I
successful in isolating just the element I want. I found
a registry error once by going through around 100,000
entries :-/ Not something I particularly want to repeat.

Pluses: The answer might be in there

Minuses: Needle in a haystack

And I'm only recommending this, if your browser seems to be
doing something different than mine. Which is possible, as
we could be using different browser versions and they may have
mucked about with stuff.

Also, there's no reason the foxnews webpage served to me,
has to be identical to the one served to you. I know that
once they geolocate me to Canada, they salt the web page
with some "sucker" Canadian articles. Like maybe my
Prime Minister making a fool of himself. The pages aren't
likely to be identical in that sense.

I don't see a reason for them to be using Akamai player
in Canada and BrightCove in the USA, but there is always
the possibility you're seeing different things than I am.

In which case, ProcMon analysis is the "last option" for
narrowing down the troublemaker file.

Paul



As I said, I'll just have to live with it. I'm not
interested in looking for a needle in a haystack.

Thanks,
Robert