Tatsh / instagram-archiver / 25641053043 / 2

100%

master: 100%

push

github

constants: send modern Chrome UA with matching client hints

The previous commit pinned ``USER_AGENT`` to a 2018-vintage Chrome 69
string to dodge Instagram's ``User-Agent`` ↔ ``Sec-CH-UA*``
consistency check. That worked, but reading "Chrome 69" in our
outgoing requests is also a fingerprint-stale flag and the docstring
asked future maintainers not to "modernise" it back to broken.

Restore a current Chrome on Linux UA and add the matching
``Sec-CH-UA*`` family alongside it. Both strings are taken verbatim
from a captured browser request that Instagram successfully routed
to the JSON API, so the GREASE entry, brand-list ordering, and
full-version-list patch numbers all agree. Tested live: comments and
child-comments come back as JSON.

The ``sec-fetch-*`` and ``sec-gpc`` headers come along for the ride
since they are part of what real Chrome sends and cost nothing to
include.

Future bumps: the Chrome major version appears in three places that
must agree — ``USER_AGENT``, ``sec-ch-ua``, and
``sec-ch-ua-full-version-list``. Update all three together (or roll
back to the legacy UA in the previous commit) if Instagram's WAF
ever tightens further.

Signed-off-by: Andrew Udvare <audvare@gmail.com>

138 of 138 branches covered (100.0%)

Branch coverage included in aggregate %.

1073 of 1076 relevant lines covered (99.72%)

1.0 hits per line