QWebEngine: Websockets from Javascript have "null" origin

[vic.ju]

Hello fellow Qt Developers,

I stumbled across a change in the Qt Webengine Chromium web sockets origin. Now I don't know if this is a bug or the expected behaviour.

Creating a websocket from a local html Javascript in the webengine produces different origins starting with Qt 6.3

• Before Qt 6.3 (tested with 6.2.4):
  The origin was properly set to "file://"

• Since Qt 6.3:
  The origin returns "null"

I created a test project that spawns a Websocket server and a web view that loads a local html. The webpage creates a web socket in Javascript and connects back to the Qt websocket server so that we can easily take a look at the connection origin.

websocketstest.zip - 4 KB

AFAIK there is no way to change the origin from the Javascript and "null" is not the correct origin. If this is a bug I will report it on the bug tracker, but I wanted to check first in the forum.

Best,
Victor

[vic.ju]

This post is deleted!

[vic.ju]

As @tiptronic pointed out to me, it looks like the origin null is the proper result and file before was a bug.

From the Mozilla documentation:

The Origin header value may be null in a number of cases, including (non-exhaustively):

• Origins whose scheme is not one of http, https, ftp, ws, wss, or gopher (including blob, file and data).