we have the situation, that chrome on mobile devices sometimes cancels a request. We have never seen the issue on a desktop chrome or other mobile browsers. The request is part of a set of redirects (oauth login) within a CORS_REQUEST. The request seems to be cancelled after HTTP_TRANSACTION_READ_HEADERS. We dumped the headers on server side but could not see an obvious difference between request that get cancelled and the ones that are completed successfully.
We first saw the problem with version 114. It also happens with 115. It happens on android and iOS.
How would we go about debugging this issue (or where could we ask if not on this list)?
We are not very used to reading netlogs, but think this is the relevant part.
t=23561 [st=692] +HTTP_TRANSACTION_SEND_REQUEST [dt=2]
t=23561 [st=692] HTTP_TRANSACTION_HTTP2_SEND_REQUEST_HEADERS
--> :method: GET
:authority:
mgr.domain.com :scheme: https
:path: /session/callback?code=YhIV9mL9YzR-FUEwWWvvpIN79hXDARB56t7HczMyBSQ.vqYIlLmsbd5r37OsXCJoSjmp-8OK6hWs5Iv4hrt0Oh4&scope=openid+profile+email+offline_access&state=-2mU16OXq-CraJNYOttoVw
cache-control: max-age=0
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
114.0.0.0 Mobile Safari/537.36
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
sec-fetch-site: same-site
sec-fetch-mode: navigate
sec-fetch-user: ?1
sec-fetch-dest: document
sec-ch-ua: "Not.A/Brand";v="8", "Chromium";v="114", "Google Chrome";v="114"
sec-ch-ua-mobile: ?1
sec-ch-ua-platform: "Android"
referer:
https://auth.domain.com/ accept-encoding: gzip, deflate, br
accept-language: de-CH,de;q=0.9,es-ES;q=0.8,es;q=0.7,de-DE;q=0.6,en-US;q=0.5,en;q=0.4
cookie: [324 bytes were stripped]
t=23563 [st=694] -HTTP_TRANSACTION_SEND_REQUEST
t=23563 [st=694] HTTP_TRANSACTION_READ_HEADERS [dt=179]
t=23742 [st=873] -CORS_REQUEST
t=23743 [st=874] CANCELLED
t=23744 [st=875] -REQUEST_ALIVE