User:KaiRo/Dynamic UA Spoofing Mechanism: Difference between revisions

m
Line 10: Line 10:
=== Backend ===
=== Backend ===


*The backend code needs to hook into sending HTTP requests to websites and adjust the UA header depending on the domain the request is being sent to.
*The backend code needs to hook into sending HTTP requests to websites and adjust the UA header depending on the domain the request is being sent to.<br>For this, it looks into a locally stored list of domains, and if the currently requested domain is on that list, it uses the spoof technique being specified in the list. This can be adding " (like Firefox)" to the string or something like that, up to using a fully custom UA string specified by the list.
<br>For this, it looks into a locally stored list of domains, and if the currently requested domain is on that list, it uses the spoof technique being specified in the list. This can be adding " (like Firefox)" to the string or something like that, up to using a fully custom UA string specified by the list.
*Additionally, the backend code needs to be able to automatically fetch new spoofing lists from the server through techniques similar to what Firefox' phishing filter or auto-update functions use.
*The backend code also needs to be able to automatically fetch new spoofing lists from the server through techniques similar to what Firefox' phishing filter or auto-update functions use.


=== Frontend ===
=== Frontend ===
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits