1690881 - Content scripts with XHR sent origin as a null. (newest version of browser)

Status: RESOLVED DUPLICATE of bug 1685570

(WebExtensions :: Request Handling, defect)

Description

[Bobby]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36

Steps to reproduce:

Hi,

We saw a problem regarding to origin while sending XHR requests. The same problem for every website like Facebook, Twitter, Instagram, Google.
The code of tested extension was the same for both versions. On older everything is fine.
Manifest of course with all necessary permisions ex.("://twitter.com/","://www.twitter.com/").
Requests sending as "NULL" are not supported by websites.

Actual results:

Request headers for firefox 72.0.2 (x64)

---

Host: twitter.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Accept: /
Accept-Language: pl,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br
Content-type: application/x-www-form-urlencoded
Content-Length: 2493
Connection: keep-alive

Request headers for firefox 85.0 (x64)

---

POST /api HTTP/2
Host: twitter.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0
Accept: /
Accept-Language: pl,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br
Content-type: application/x-www-form-urlencoded
Content-Length: 2493
Origin: null
Connection: keep-alive

Expected results:

Origin has to be correctly replaced depends on specific website.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 3

[John]

Any idea when this can be fixed? Its causing some serious issues for my product and it would really help if this was resolved...