Proxy gateway url filtering based on the user's login RRS feed

  • Question

  • Hello I am also planning to create a firewall by my own.

    And I succeded in configuring a proxy on local machine using c#, but i dont know to configure a proxy on local LAN. and I have to communicate that proxy server with local machine so i can filter based on the user's login.

    I dont know how to do by WCF or by Windows application or Web application. could anyone just give me a hint that from where should i start.

    • Moved by Marvin_Guo Friday, February 28, 2014 6:13 AM better forum
    Thursday, February 27, 2014 5:30 AM

All replies

  • Start to ask this in a forum which deals with your problem.

    In an analogy you ask currently at a butcher how to bake a bread.

    This is the forum for the destop user interface Windows Forms and its classes (or API's)

    You can for instance start here.


    Thursday, February 27, 2014 8:39 AM
  • Hi,

    You question is not so clear. However, i assume that you want to filtering URL.

    You can try "IIS 7.0 Request Filtering and URL Rewriting". IIS 7.0 and above includes a request filtering module that is based on the URLScan ISAPI Filter for IIS 6.0. The module helps you tighten security of your Web servers. In a nutshell, IIS 7.0 is well behaved. In the request processing pipeline, the request filtering module gets a higher priority than the rewriter module. The rewriter module also has a sufficiently high priority in the request processing queue (otherwise it wouldn't be a very useful module), but it still kicks in after request filtering module on the BeginRequest path. The important takeaway here is that this is the desired order of processing, and so if you are manually tweaking module order and priority in configuration, swapping the order of these two could be considered as breaking the security contract that request filtering tries to establish.

    If you want to customize this function. You can consider to check request URL and User information in HTTP Module. An HTTP module is an assembly that is called on every request made to your application. HTTP modules are called as part of the ASP.NET request pipeline and have access to life cycle events throughout the request. HTTP modules therefore give you the opportunity to examine incoming and outgoing requests and take action based on the request. The topics in this section provide information on how HTTP modules work and how to create them.

    Wednesday, March 19, 2014 2:52 PM