Edge doesn't support referrer meta tokens when video is requested

Issue #12457205 • Assigned to James M.

Details

Author
samuel v.
Created
Jun 23, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

On a page that has the referrer meta token on always, edge does not pass the referrer in video elements.

I’ve uploaded screenshots of the requests by chrome and the one from edge

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. We are unable to reproduce this problem in Edge. Please update this case when you can provide us with a sample to test. Thank you so much for your assistance with this issue.

    Best Wishes,
    The MS Edge Team

  • http://camendesign.com/code/video_for_everybody/test.html

    this is not something we wrote but it shows pretty much the same behavior

  • http://azrinst02396.northcentralus.cloudapp.azure.com/test/

    this page is pretty much what we do. The video won’t load in both Chrome or Edge. (Because server side there is a check on the referrer, which is now no longer correct)
    But at least you can see that in Chrome there is a referrer in the head, in Edge it’s lacking.

  • http://azrinst02396.northcentralus.cloudapp.azure.com/test/test.html

    this one will play in both Chrome and Edge, but Chrome passes the Referrer in the headers, Edge does not even though the header specifically contains :

  • Hello,

    Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge. Please test this behavior in our latest creator’s update 15063 or the insider build 16232.

    Best Wishes,
    The MS Edge Team

  • Are you telling me that, while using Edge 40 you can see in the Developer Tools the Referer Request Header is set??
    Because here i can’t see that Referer Header.
    And I installed a clean machine for this to make sure nothing in my environment is affecting this. Just telling me I’m supposed to upgrade to an Insider Build without any further information is very unhelpful and the only thing that will accomplish is that our team will just have to tell our customers that next to IE not being supported Edge won’t be supported as well. And again exactly for the same reasons like not supporting IE… not adhering to standards…

  • BTW, i’m running Windows 10 PRO Version 1703 (OS Build 15063.413)

  • Hello,

    My apologies; I meant to mention that I have attached a screenshot of what I am seeing to help communicate. There is no 400 error and no referrer header showing in any other browsers. Please check the screenshot and then provide an update.

    Best Wishes,
    The MS Edge Team

  • Hello,

    Is it possible I don’t see the screenshot you are mentioning?

    Regards, S.

  • Hello,

    Please try now.

    Best Wishes,
    The MS Edge Team

  • We have the same issue here. Edge in the Creators Update package does’n send referer request header when requesting the video file. This causes problems in our system, because some functionality depends on the referrer header value.

    With earlier versions of Edge we had no problems in the past.

You need to sign in to your Microsoft account to add a comment.

Sign in