1610166 - Audio player cookies are not being sent on parts requests

Status: RESOLVED DUPLICATE of bug 1532722

(Core :: Networking, defect)

Description

[shmulik.shnoll]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36

Steps to reproduce:

We have a page with an audio player element, to get some streaming audio.

Actual results:

The first request for the audio source is ok, but following requests from the player, for additional streaming data, is sent out to the server without the cookies header.

Expected results:

Cookies should be sent to the server with every request to streamed data (as it was until recently).

Comment 1

[Rares Doghi, Desktop QA]

Hi [e-mail] can you please provide the page this issue occurs on and a few steps on how to reproduce the issue ourselves and where to check the Actual results ?
Also does this issue occurs in our latest nightly build ? you can find it here: https://nightly.mozilla.org/

Comment 2

[shmulik.shnoll]

Hi,
Sorry for the late reply...
No, this is not a nightly build.
Get it as a ticket from one of our customers, and it reproducible and happens on our own PCs also.
We are having a page that let the user hear/view an audio/video recorded call.
This used to work, and just stop working lately (only on FF).
We also have an external version of this page, where users can share the call externally, but there since you do not have to be logged in, we do not need the cookie, and everything is working fine.....

Here you have a url to see the issue:
https://app.gong.io/call?id=9065826164117622662
Login as :
user: [e-mail]
password: BugFirefox123

Comment 3

[shmulik.shnoll]

I've just installed the Firefox nightly build , and it seems this issue is resolved.
When it the plan for a release?

Thanks,
Shmulik

Comment 4

[Rares Doghi, Desktop QA]

Thanks for the extra info, I managed to reproduce this issue using the provided URL, and in the developer tools in the Network tab on Release and Beta I was getting the 302 code for the requests while on Nightly I got the 200 Ok code

Comment 5

[shmulik.shnoll]

Exactly.
The 302 you got, is because the cookie was not sent to the server, and the server as a response sent a redirect....
Looking forward for the release of Firefox 74.....

Thanks.

Comment 6

[Valentin Gosu [:valentin] (he/him)]

Honza, did we change cookie handling on redirects recently?