User Agent Spoofing
The user agent identifier typically includes information such as the application name, version, host operating system and so on. Yours can be found below:
ArchiveTeam ArchiveBot/20141009.02 (wpull 0.1002a1) and not Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36
You should no longer have to use user agent spoofing, but there were times that one particular webbrowser dominated the Internet, and that was Internet Explorer. Some web-authors however are still not using up-to-date browser sniffing, and that's when browser spoofing might come in handy (or for testing).
What is it for?
There's another reason for having HTTP user agents, and that is the raising number of Internet capable deviced. Like the iPhone with a resolution of only 480-by-320-pixel. Which isn't exactly the average resolution for desktop monitors. And that is why web-authors need to know what you are using — to change the layout or to reduce the font-size (just some examples).
MultiZilla enables you to spoof the HTTP User Agent, and that can be done like with help of MultiZilla's User Agent Manager:
Limitations
The current implementation is limited to HTTP spoofing only, because SeaMonkey futured an important bug. Web authors can still check: navigator.appName, navigator.appVersion, navigator.language and navigator.platform with JavaScript, because of SeaMonkey bug 115773.
Troubleshooting
There are some things to keep in mind. The first one, and this is the most important one, is that you need to close/exit SeaMonkey, inclusing quickstart, before you can edit multizilla.rdf.
Note: visit our newsgroup or mailing list in case of trouble/questions.
Tip
Please file bug reports for website that won't work without user agent spoofing in bugzilla.mozilla.org (component "Tech Evangelism") after you searched for possible duplicates — you might after all not be the first person to run into this problem.
