Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
User:KaiRo/Dynamic UA Spoofing Mechanism: Difference between revisions
User:KaiRo/Dynamic UA Spoofing Mechanism (view source)
Revision as of 02:24, 19 September 2007
, 19 September 2007add discrimination idea
m (→Backend) |
(add discrimination idea) |
||
| Line 1: | Line 1: | ||
The goal of this project is to implement a solution that dynamically adjusts the User-Agent ("UA") HTTP header depending on which domain the data is being requested from, along with a mechanism to encourage users to actively take part in evangelizing. | The goal of this project is to implement a solution that dynamically adjusts the User-Agent ("UA") HTTP header depending on which domain the data is being requested from, along with a mechanism to encourage users to actively take part in evangelizing. | ||
Spoofing should only be used on websites that close out affected user agents unnecessarily without compelling reasons to do so, enabling small extra features on websites or entering websites that have good reason for closing out certain browsers are no target for this mechanism, at least not at this point. | Spoofing should only be used on websites that close out affected user agents unnecessarily without compelling reasons to do so, enabling small extra features on websites or entering websites that have good reason for closing out certain browsers are no target for this mechanism, at least not at this point. | ||
It might be a good idea to extend this even as far as the feature being available as an extension for a greater number of browsers, and showing a "this page discriminates users of some browsers against others" warning even in browsers that do work with a page, with a "more info" button that leads to the web service describing which browsers are discriminated in which way. | |||
This should be achieved through client-side code that is in the mozilla.org source code repository and built into the SeaMonkey suite by default (but also available to any other browser) as well as server-side code available from some public repository, which we will try to get deployed on some Mozilla server. All the code should be licensed under the standard Mozilla tri-license (MPL/GPL/LGPL). | This should be achieved through client-side code that is in the mozilla.org source code repository and built into the SeaMonkey suite by default (but also available to any other browser) as well as server-side code available from some public repository, which we will try to get deployed on some Mozilla server. All the code should be licensed under the standard Mozilla tri-license (MPL/GPL/LGPL). | ||