Core concepts

fluxzy is an intermediate HTTP agent that acts as man on the middle. It uses a combination of filter and action to collect network datas and to process alteration. A combination of a filter and multiple actions is called rule.

A rule is at the center of fluxzy and it's main the starting point to manage and alter specific par of the HTTP flows passing through fluxzy.

A filter is a particular configuration that isolate a special HTTP traffic. The selected result can be used later for displaying purpose or for applying alteration rule named "action".

An action is anything one can operate to modify the behaviour of an HTTP exchange. It can be an alteration on HTTP level, such as adding extra HTTP header, to a transport configuration modification, such as forcing an IP address resolution.

A fluxzy action is not limited to the current HTTP context and can interoperate with external tools via process execution (see ExecAction).

A FilterScope is a particular timing where a Filter or an Action can be evaluated. It's mechanism to ensure coherency between those two. For example, in order to change a response header, the response header must have been received.

When this rule is violated, you will have a FilterOutScope error at some point.

Fluxzy supports the main following filterscope:

• OnAuthorityReceived : This scope denotes the moment fluxzy is aware the destination authority
• RequestHeaderReceivedFromClient : This scope occurs the moment fluxzy parsed the request header receiveid from client
• RequestBodyReceivedFromClient : This scope occurs the moment fluxzy received fully the request body from the client
• ResponseHeaderReceivedFromRemote : This scope occurs the moment fluxzy has done parsing the response header.
• ResponseBodyReceivedFromRemote : This scope occurs the moment fluxzy received the the response body from the server.