If your web application passes content over standard protocols and over SSL, you might want to create a dedicated pipeline to handle the SSL traffic first, before it is passed through the standard pipeline for processing. This pipeline might be responsible for the removal of sensitive information.
When the pipeline has completed its manipulations, it can then forward to the pipeline that handles standard traffic for general pipeline activities.
- Create the
- Specify all of the session agents needed for the SSL-only traffic.
Typically, the SSL pipeline strips out any sensitive information.
- After you create the chain of SSL-only session agents, set the following value in the
- In the
[Socket]section, specify the following properties to point to the start of the standard pipeline. If you are using a port that is not
1966, insert that value in the location below:
Server=localhost Port=1966 UseSSL=False
- Create the second pipeline for port
1966in standard fashion.
- When you have created both pipelines, SSL traffic is passed through the SSL pipeline first, which then forwards it to the
port=1966pipeline for standard processing.