@surendarchandra wrote:
According to https://bugs.chromium.org/p/chromium/issues/detail?id=673315, looks like this is a problem with HPACK processing. This doesn’t seem to affect Safari. Would 10.1.10 fix this? Any ideas? It used to work fine until recently; not sure what changed. Thanks
Posts: 1
Participants: 1