Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Akamaihd.net ruleset breaks ooyala videos #9052

Closed

Description

@Leonick

In my particular case I'm trying to watch the premium videos at tested.com, the akamaihd.net ruleset break the videos.

When checking now the video was streamed from 94890ooyala-a.akamaihd.net

Activity

  1. numismatika commented on Mar 13, 2017

    @numismatika
    Contributor

    Any mixed content or CORS warnings?
    Is the OOyala rule active too?
    Are there network requests to api.ooyala.com?

  2. Leonick commented on Mar 14, 2017

    @Leonick
    Author

    Clicking play gives this in web console:
    GET XHR http://player.ooyala.com/player/all/B3dzY5OTE6_YMfk1WrB7y_nm4UmraSTx_1800.m3u8 [HTTP/1.1 200 OK 0ms] Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://94890ooyala-a.akamaihd.net/B3dzY5OTE6_YMfk1WrB7y_nm4UmraSTx/HbKJtGy6IOu2wtc_6QWgqKq385rvEfCn6PpX4k4l_MHsyAmipQwGo4sFcPJelwWB/0.ts. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘(null)’).

    Network log says Access-Control-Allow-Origin is "*".

    The OOyala rule is inactive as Tested forces http on all pages but the login page.

    No requests to api.ooyala.com, only player.ooyala.com.

    Disabling Akamai rule makes video play in Firefox. Noticed last night that it works in without disabling any rules in Chromium based browsers.

  3. numismatika commented on Mar 14, 2017

    @numismatika
    Contributor

    This null comparison seems weird, not sure where it comes from.

  4. numismatika commented on Mar 15, 2017

    @numismatika
    Contributor

    Enabling OOYala doesn't fix it?

  5. Leonick commented on Mar 16, 2017

    @Leonick
    Author

    No, forcing the ooyala ruleset only breaks the player further as tested is forcing itself to be http.

    • player.ooyala.com
      Player JS correctly chooses secure player based on parent document
      protocol, but fails if parent document is HTTP and player is rewritten to
      HTTPS. Therefore, only enabled on mixedcontent platforms.
  6. Bisaloo commented on Apr 29, 2018

    @Bisaloo
    Collaborator

    All CORS issues will be fixed in the next release by #15157. Please reopen if you still have issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions