How to remove X-Forwarded-For

If you want to remove X-Forwarded-For received by the host application, then a pre-cache REQMOD service may suffice. Clone the virgin request and use the libecap::Header::removeAny() method to remove the offending header from the cloned/adapted message. Do not forget that request may have bodies and that adapters modifying headers are currently responsible for body delivery to the host application.

If you want to remove X-Forwarded-For added by the host application before forwarding the request to the next HTTP hop, then you need to make sure your host application supports post-cache REQMOD adaptation services and lets them have the last word. For example, Squid does not support post-cache REQMOD.

Any decent host application using and/or adding X-Forwarded-For should have a knob to disable those features. Investigate them before writing any adapter code because such native support is usually more efficient and may support vectoring points where there is no eCAP support. For example, Squid has forwarded_for and follow_x_forwarded_for configuration directives.

Thanks Alex for your reply.. i will try it out