1318772 - Websockets closed with 400 Bad Request

Status: RESOLVED INVALID

(Core :: Security: PSM, defect)

Description

[The 8472]

Attachment: browser console output

STR: 

fails:

- start nightly profile manager
- create and start new profile
- open browser console
- open https://meguca.org/all/
- observe a request to https://meguca.org/socket returning "400 bad request"

works:

same as above, except with release (50). response status code is "101 switching protocols"

Comment 1

[The 8472]

Attachment: same request except on release

Comment 2

[Michal Novotny [:michal]]

It stopped working when TLS 1.3 was enabled in bug 1310516. I have no idea where the problem can be. Martin, can you have a look at it?

Comment 3

[Martin Thomson [:mt:]]

The problem here isn't directly related to TLS 1.3, the connection is successfully made, but more something to do with the connection after the connection completes.  I think that this is likely to be a cloudflare issue.  I'll contact them and see.

Comment 4

[Martin Thomson [:mt:]]

OK, that was quick.  Cloudflare have confirmed that they are aware of an issue and are working on it.

Comment 5

[Honza Bambas (:mayhemer)]

Can we now close this bug?

Comment 6

[Michal Novotny [:michal]]

Server side issue. Closing as invalid.