Post Reply 
Can't get the GET header filter to work.
Jul. 12, 2005, 10:57 AM
Post: #12
 
Well thanks sidki, that certainly works but I had to play with it a bit. In the end it was just wildcards either side of the word that did it - eg. *MyName* I set up one filter each for my first and last names and one for my IP address.

This just kills the entire URL request, not what I was expecting, but it does the job and will suffice for now until I get to grips with Proxomitron. Thanks for your time. Any idea now how I can kill a URL when the GET or POST headers exceed a certain length?

I’ve been watching and modifying headers for about 5 years now with A4Proxy and I’ve seen all sorts of things inserted in GET and POST headers. I’ve seen some of amazing length and it’s obvious that they are not just requests for web pages or components of those pages. Information is going out and it could literally be anything that you have on your computer. Apps and active content can do this, as well of course as viruses/trojans etc. I keep a well locked down and clean system and the GET and POST headers is the last thing I don’t have full control over.

Shaman
Quote this message in a reply
Post Reply 


Messages In This Thread
Can't get the GET header filter to work. - Shaman - Jul. 07, 2005, 07:30 PM
[] - Oddysey - Jul. 09, 2005, 02:38 AM
[] - z12 - Jul. 09, 2005, 06:38 AM
[] - Shaman - Jul. 10, 2005, 11:08 PM
[] - Oddysey - Jul. 11, 2005, 02:19 AM
[] - Shea - Jul. 11, 2005, 02:57 AM
[] - Shaman - Jul. 11, 2005, 09:45 AM
[] - sidki3003 - Jul. 11, 2005, 03:49 PM
email... - ProxRocks - Jul. 11, 2005, 04:28 PM
[] - sidki3003 - Jul. 11, 2005, 05:12 PM
this subject line is dumb... - ProxRocks - Jul. 11, 2005, 05:52 PM
[] - Shaman - Jul. 12, 2005 10:57 AM

Forum Jump: