[HTTPS-E Rulesets] Broken Edgecast rule for vidyard.com

[Tyler Campaigne]

Hello,

Our HTTPS Edgecast URLs are 404ing on the redirect. As an example file,
https://gs1.wpc.edgecastcdn.net/8061DD/mirror_assets_production/javascripts/amplify.store.min.js
is redirecting to
https://ne.wac.edgecastcdn.net/8061DD/mirror_assets_production/javascripts/amplify.store.min.jswhich
is a 404 for our Edgecast account.

Our HTTP links work perfectly fine with the current ruleset, just the HTTPS
ones seem to have broken rules for us.

I guess the main question I have is why the Edgecast rules are set up for
requests that are already over HTTPS, as it seems redundant. As well, I'm
not sure what a custom rule for our site would be, since the
gs1.wpc.edgecastcdn.net domain appears to be too general to make a custom
rule for.

Any advice as to how to fix this for our site would be greatly appreciated!

Cheers,
Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere-rules/attachments/20130723/eb43986c/attachment.html>