A proper way to put code before </head> tag

[JJoe]

What is the actual user agent that was changed to "Space Bison/0.02 [fu] (Win67; X; SK)"? I don't see that here yet or remember it.

To answer the question, the exceptions lists run before a user-agent header filter sets the variable hOrigUA. hOrigUA eventually contains the original User-Agent.

I think something like

Code:

www.google.(*/)+{1}search\? (
  $OHDR(user-agent:*msie 6) $SET(0=a_ads.a_target.i_popup_b:0.i_timer:2.i_noscr:3.f_ua_§Mozilla/1%2e22 (compatible; MSIE 7%2e0; Windows NT 6%2e1).)
  |$SET(0=a_ads.a_target.i_popup_b:0.i_timer:2.i_noscr:3.)
  )

in Exceptions should do what you want.

In Exceptions-U

Code:

www.google.(*/)+{1}search\? $OHDR(user-agent:*msie 6) $SET(0=f_ua_§Mozilla/1%2e22 (compatible; MSIE 7%2e0; Windows NT 6%2e1).)

A header filter could also work. The problem that I see with header filters is that their order of application can be important and my Win7 machine doesn't always put new ones where they belong.

Code:

[HTTP headers]
In = FALSE
Out = TRUE
Key = "! * 999 User-Agent: fake IE7 for IE6 for OZO (Out)"
URL = "www.google.(*/)+{1}search\? $OHDR(user-agent:*msie 6)$SET(keyword=$GET(keyword)f_ua_§Mozilla/1%2e22 (compatible; MSIE 7%2e0; Windows NT 6%2e1).)"

Seems to order correctly after saving the new config several times and work.

The set's documents are in the "sidki-etc" folder. You should be able to access them by opening the Proxomitron's Web Page filter editor and testing the filters in the "NAOKO 4.5 CONFIG -- SIDKI 2010-10-23 -- README" section. Also, available at http://sidki.proxfilter.net/prox-docs.html or http://sidki.host22.com/prox.html .

HTH