On 9/5/2019 9:02 AM, Paul B. Gallagher wrote:
Based on info received here, I created a user.js (never had one before)
so I could pass a different UA to one particular problem site. But I
can't tell if it's working. Is there a way to confirm that the site's
getting what I'm feeding it? Help | About just reports the standard UA.

I placed the file here:
C:\Users\(Windows
Username)\AppData\Roaming\Mozilla\SeaMonkey\Profiles\(profilename).default\

The part you've replaced with "(profilename)" is usually just random. The "default" part is typically what you see as the name in profile manager. If you've never created additional profiles there's probably only the one default directory there anyway, but just mentioning in case not.

And here's the content, did I get it right?

# Mozilla User Preferences

user_pref("general.useragent.override.viki.com", "Mozilla/5.0 (Windows
NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0");

As a quick check that you've correctly edited the correct file:
- From within SeaMonkey open <about:config> and accept the warning
- Type "override" in the search box at the top
- Does your override preference show up there?

Personally I don't usually bother with directly editing the prefs files, and just update them via about:config. There are pros and cons though, so whichever way you prefer is fine.

David E. Ross wrote:
1.  Go to the Web site of your concern.

2.  With the Web page for the site still in SeaMonkey's window, on the
SeaMonkey menu bar, select [Help > About SeaMonkey] or [Help >
Troubleshooting Information].

Either of those will display your current user agent string.

I don't think that picks up site-specific overrides. Certainly for me, if I go to a site for which I know the override is working (otherwise the site doesn't render correctly), both of those still show my default UA.

A more complicated method involves installing the "Live HTTP headers"
extension and capturing the headers sent (and also received) when you go
to the site.

There's not really any need for the extension any more, since similar functionality is built in: - Go to Tools > Web Development > Toggle Tools; the tools open at the bottom of the window
- Select the "Network" tab
- Load (or reload) the target page (viki.com)
- Select the top request in the list on the left of the "Network" tab
- The request and response headers are listed on the "Headers" tab on the right - Check the "User-Agent" request header; if your override works you should see that string (with no mention of SeaMonkey), otherwise you'll see the default one with the SeaMonkey version

--
Mark.

_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to