InformAction Forums

Try to play a video which requires whitelisting brightcove.com

Example: http://www.dailymail.co.uk/femail/artic ... -visa.html

The video will play with this rule: But none of them works: I'm curious.
I thought it was identical by putting both sites in the same "Accept" line and putting them separately.
Why? What is the cause?

ReporterX wrote:But none of them works:

Code: Select all

Site .brightcove.com
Accept from .brightcove.com
Accept INCLUSION from .dailymail.co.uk
Deny INCLUSION

^^ Strange, that's probably what I would have tried to use.
No time to check this myself atm, sorry, so can you please try this rule, and post here the message you see from ABE in the Browser Console (Ctrl-Shift-J) when it doesn't work?

barbaz wrote:

ReporterX wrote:But none of them works:

Code: Select all

Site .brightcove.com
Accept from .brightcove.com
Accept INCLUSION from .dailymail.co.uk
Deny INCLUSION

^^ Strange, that's probably what I would have tried to use.
No time to check this myself atm, sorry, so can you please try this rule, and post here the message you see from ABE in the Browser Console (Ctrl-Shift-J) when it doesn't work?

No problem, and I just tested all 3 ABE codes. Here is the messages:

First (Accept from .brightcove.com + Accept INCLUSION from .dailymail.co.uk)
http://pastebin.com/uYFEzApS

Second (Both Accept INCLUSION but separate lines)
http://pastebin.com/KkCK0SvJ

Third (Accept INCLUSION from SELF+ SELF++ .dailymail.co.uk)
http://pastebin.com/e7bKx1N7

P.S. It hits the anti-spam filter so I have to past the whole message elsewhere.

OK, I'm not completely sure but I think it's related to the fact the brightcove resource requested by dailymail redirects to another brightcove resource, so if dailymail and brightcove aren't together then ABE thinks the request isn't something you want because one the redirect URLs doesn't match the Accept line hit initially.
(Would be helpful if someone who knows for sure could confirm?)

I can confirm that redirections cause ABE to behave differently, and often require the sites to be on the same line.

I ran into this a while ago at work, when following links from our team wiki to a local development server, which then redirected to another local URL. It wasn't enough to have I had to have