I can receive the request from the browser, but I don't know how to send the data back to the browser. I don't know if I am supposed to send it back through the same port I received it from and if I need to send the browser a header etc. etc. etc.

I've looked for information on the dirt of how proxies work, but all I can find is "browser sends request to proxy, proxy send request to server blah blah blah" I need to know some real, hardcore information on how they truly work and tick.

Can anyone give me some information on how to make a proxy?

------------------
~~~boogie woogie woogie~~~
Jesus didn't come to save the saints.

That doesn't help you with proxy stuff, though since it was on a related topic, I thought I would bring it up. I'll likely make another post about it sometime to see how much interest there would be in such a thing.

Cheers!

--clint

Clint, that sounds cool too. I will eventually make my filter software cross-platform as well, ... if I ever get it to work on windows first!

------------------
~~~boogie woogie woogie~~~
Jesus didn't come to save the saints.

Anyways, Does anyone know how I can make this work with out setting it up as a proxy? I need this to work in a way that people can't just turn it off. How can I make the filter jump out in front of incoming web requests so I can check the page to make sure it's ok to view?

------------------
~~~boogie woogie woogie~~~
Jesus didn't come to save the saints.

quote:

---

Originally posted by bwoogie:
Anyways, Does anyone know how I can make this work with out setting it up as a proxy? I need this to work in a way that people can't just turn it off. How can I make the filter jump out in front of incoming web requests so I can check the page to make sure it's ok to view?

---

Aaah. This is quite a bit trickier to do.

I've looked into doing this same thing before, and the only lead that sounded promising to me was to write it as a hook that inserts itself as a hook into the TCP/IP protocol stack. This is the same technique that firewalls use to block incoming/outgoing requests. On POSIX systems (Linux/BSD/Unix), I *think* these are called PFIL hooks. I'm trying to remember what they're called on Windows...
*spends a few minutes on Google...*

Okay. A thing that looks like a good start might be this overview from NDIS called Windows Network Data and Packet Filtering. It goes over what methods there are for packet filtering on Windows XP and 2000.

There is an extremely good looking article on Code Project called An Adventure: How to implement a Firewall-Hook Driver?, and it looks like it might be a great sample project for you to start with.

Microsoft also has a long document explaining how the Windows Firewall works, but that might be less relevant to you.

Something else that looks good is called "IP Firewall Hook", it's supposedly an open-source COM component that can be used to develop firewall apps, but it looks like the homepage is down. However, I think I found it available for download here should you like to try it out.

Okay, that's enough for now -- hopefully I didn't swamp you with information.

Cheers!

In Christ,
clint

Edit: This Microsoft article looked too good to not pass on -- it's more of an official document on how to implement Firewall apps.

[This message has been edited by HanClinto (edited May 01, 2007).]

------------------
~~~boogie woogie woogie~~~
Jesus didn't come to save the saints.