Viewing 1 replies (of 1 total)
  • Thread Starter dandante

    (@dandante)

    I figured out a workaround to this.

    Basically, I just tell the standalone player to go to some url that I control.
    That URL then does an http redirect to the long complex URL that cannot be changed (which the standalone player was changing deep in its internals).

    Luckily the standalone player can follow redirects and this works just fine.

    Dan

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: Audio Player] trouble with S3 signed URLs in standalone player’ is closed to new replies.