Change Details

We should collect Client Hints data when users log in. This will allows CheckUsers to match this data against other accounts as part of a CheckUser investigation. We currently send client hint header data when a POST request is made to login. We should remove the headers sent on this page, as the data that is sent is not collected. This will be replaced with a use of the JavaScript API. ========Acceptance criteria * [ ] When a user logs in, CheckUser creates rows in `cu_useragent_clienthints_map` if the browser supports Client Hints

We should collect Client Hints data when users log in. This will allows CheckUsers to match this data against other accounts as part of a CheckUser investigation. We currently send client hint header data when a POST request is made to login. We should remove the headers sent on this page, as the data that is sent is not collected. This will be replaced with a use of the JavaScript API. ========Acceptance criteria * [ ] When a user fails to log in, CheckUser creates rows in `cu_useragent_clienthints_map` if the browser supports Client Hints * [ ] When a user logs in, CheckUser creates rows in `cu_useragent_clienthints_map` if the browser supports Client Hints

We should collect Client Hints data when users log in. This will allows CheckUsers to match this data against other accounts as part of a CheckUser investigation. We currently send client hint header data when a POST request is made to login. We should remove the headers sent on this page, as the data that is sent is not collected. This will be replaced with a use of the JavaScript API. ========Acceptance criteria * [ ] When a user fails to log in, CheckUser creates rows in `cu_useragent_clienthints_map` if the browser supports Client Hints * [ ] When a user logs in, CheckUser creates rows in `cu_useragent_clienthints_map` if the browser supports Client Hints