Forum Discussion

Doran_Lum_13484's avatar
Doran_Lum_13484
Icon for Nimbostratus rankNimbostratus
Sep 04, 2017

X-Forwarded for https

Hi all, we have an application on our server which can't determine if the request is https or http coming from F5. X-Forwarded option have been enabled but the issue still persist. Should

 

I have try with the irule below for X-Forwarded-Proto but somehow I got an error.

 

I have also try to insert "https" for Request Header Insert but the issue still persist.

 

application delivery
BIG-IP
LTM

2 Replies

Sort By
  • oscarnet_69487's avatar
    oscarnet_69487
    Icon for Nimbostratus rankNimbostratus
    Sep 04, 2017

    HI

    you miss 

    }
    in end

    when HTTP_REQUEST { 
    if { [ssl::mode] == 1 } {
        if {!( [HTTP::header "x-Forwarded-Proto" ] eq "https") }{
            HTTP::header insert x-Forwarded-Proto "https"
            }
        if {!( [HTTP::header exists "x-Forwarded-Port" ]) }{
            HTTP::header insert x-Forwarded-Port [TCP::local_port]
            }
        }
    }

    have a good day!!!

  • Kai_Wilke's avatar
    Kai_Wilke
    Icon for MVP rankMVP
    Sep 05, 2017

    Hi Doran,

    you could streamline your iRule by moving the protocol enumeration into the 

    CLIENT_ACCEPTED
    event (triggered only once every TCP connection), store the enumeration result into a 
    $variable
    and then reference the 
    $variable
    on every subsequent 
    HTTP_REQUEST
    event. This approach will greatly reduce the overhead for Keep-Alive-Connections.

    when CLIENT_ACCEPTED {
    if { [PROFILE::exists clientssl] } then {
        set client_protocol "https"
    } else {
        set client_protocol "http"
    }
}
when HTTP_REQUEST {
    HTTP::header remove "X-Forwarded-Proto"
    HTTP::header insert "X-Forwarded-Proto" $client_protocol
    HTTP::header remove "X-Forwarded-Port"
    HTTP::header insert "X-Forwarded-Port" [TCP::local_port]
}

    Note: In addition you should review your application if it would introduce certain risks if the client sends handcrafted X-Forwarded-Proto and X-Forwarded-Port headers to your application. If this scenario introduce some risks or if you can figure out the assosiated risks, then make sure to 

    [HTTP::header remove]
    any existing 
    X-Forwarded-Proto
    and 
    X-Forwarded-Port
    headers before 
    [HTTP::header insert]
    your verified values...

    Cheers, Kai