Web Application & API Protection

Expand all | Collapse all

WEB: X-Forwarded-For insert with custom header name?

  • 1.  WEB: X-Forwarded-For insert with custom header name?

    Posted Sep 16, 2019 04:27 AM
    Hi,

    Is it really true, that WEB cannot add custom X-Forwarded-For header directly using X-Forwarded-For Rule?

    One must use url rewriting with variable $CLIENT_IP?


    ------------------------------
    Thx
    ------------------------------


  • 2.  RE: WEB: X-Forwarded-For insert with custom header name?

    Posted Sep 16, 2019 04:31 AM

    Hi Patrick,

    FWB does support both XFF parsing and insertion.

    Best Regards

    Rafael Lehmani

    Consulting Systems Engineer,??Enhanced Technologies, INTL
    ________________________________________________

    E: rlehmani@...
    M: +33 625 115 291
    ________________________________________________
    www.fortinet.com




    *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***






  • 3.  RE: WEB: X-Forwarded-For insert with custom header name?

    Posted Sep 16, 2019 04:52 AM

    Q: Only with the URL Rewriting can we have a free form X-Forwarded-For Header name, right?

    >no, XFF can custom it (Use X-Header to Identify Original Client's IP)

    Q: Also it seems like you will add IP addresses if the header already exists (in XFF rule) but what if you just want to replace the value with the single IP that FWEB receives.

    >?? XFF?? rule is to add FWB IP@ as next hop (with or without XFF inserted before)

    Q: Seems like URL Rewriting will maybe do it?

    > no need




    *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***






  • 4.  RE: WEB: X-Forwarded-For insert with custom header name?

    Posted Sep 16, 2019 03:23 PM

    Hi Patrick,

    Could you please ask you local SE to raise a case to CSE Team by providing cnfig and pcap files?

    Best Regards

    Rafael Lehmani

    Consulting Systems Engineer




    *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***