• Resolved epresso

    (@epresso)


    Hello,

    first – hat’s off to you and your work.

    I’ve encountered a strange behaviour and I’m not sure if
    it’s related to my hosting or the way, browser (Firefox)
    handles redirections, or maybe it’s WP/MediaElement thing.

    In normal use scenario, when I’m trying to play m4a file
    (without ssp_use_raw_audio_file_url function engaged),
    the player does nothing but console returns error regarding
    wrong Content type headers (text/plain) being declared.

    Redirect doesn’t work from player level, it returns an error
    instantly. It works like a charm when called from browser’s
    url bar, using simple get or curl.

    I assume, that player tries to load redirect as an audio file
    and something doesn’t work quite well.

    I tried several tricks with php and htaccess rules but I’m
    stuck and forced to use raw_audio_file_url for now.

    Is this a feature or a bug? ?? Okay, is there any way
    to implement custom Content-type headers for
    redirection or maybe that’s a flaw that affects only
    some users and relates to their hosting configuration?

    Regards,
    Tomek

    https://www.ads-software.com/plugins/seriously-simple-podcasting/

  • The topic ‘Redirection headers and m4a file’ is closed to new replies.