Yes. At the end. What a strange way of presenting documentation. Thank you for pointing them out

Three years later is it still the case that the best thing to do is ignore the documentation and just set the Authorization header manually? I am here because I searched for URLRequest authorization when on reading the documentation fro URLRequest in a code review, after it has been in production for many weeks, that the header should not be set by hand. Then I read that Quinn recommends doing just that. We are using HTTP Digest authorisation, and it has "just worked". Now I am confused.

..

That seems to work. I asked Chat-GPT FFS. For once it did not lie to me. Chat-GPT learnt this somewhere - where is this documented?