Lee wrote:
On 9/5/19, Paul B. Gallagher <[email protected]> wrote:
[email protected] wrote:
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?
Yep. But without the https protocol as noted.
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
I followed your steps, but I see no "Headers" tab on the right or
anywhere else in the pane. The application is maximized, so there should
be nothing off-screen.
Click on one of those lines that starts off with '200 GET', over on
the right is a 'Raw headers' button, click on that and below it you
get a 'request headers' & 'response headers' panel
OK, I see what you mean. It turns out I'm not sending the site-specific
UA; will try including the version with "www." and see if that helps.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
