I’ve seen that X-Forwarded-For is not supported by Netlify and you recommend alternative headers. Specifically, looks like you provide three options: X-Nf-Client-Connection-Ip X-Bb-Ip Client-Ip We would like to use the client-ip header for our logging - is this a header you are supporting long te…

Hi there, We make no guarantees on anything except “X-Nf-Client-Connection-Ip”. Please use that one instead!

Many other companies seem to have settled on true-client-ip as a header for this purpose - is this something you could support?

Nope! We’ll be using the header names we have in place already :slight_smile:

I get that, but it makes things very difficult for our (Netlify and Discourse) common customers. We need to tell customers with proxies in front of their Discourse installation to scrub certain headers from requests before they forward them to us and we really don’t want that list to grow. Would y…

Great to hear! We use x-forwarded-for internally, so no can do on that one. Could you link me to the details on the “emerging standard” you reference? Our team would be happy to take a look at it, I just hadn’t heard of it before so not sure where you’ve seen it :slight_smile:

This type of detail would be really useful in the main Functions section of the docs. Can it be added please?

Hi there, could you be a bit more specific on which type of detail you feel should be added? thanks!

Specifically that X-Nf-Client-Connection-Ip is available to our code, what it represents, and so forth.

thanks for clarifying, i’ll do some checking!

Seems event.headers['client-ip'] has started to be undefined some time this week. I still could not find any documentation on X-Nf-Client-Connection-Ip via Google, but fortunately this thread appeared.On the other hand, event.headers['X-Nf-Client-Connection-Ip'] is also undefined for me right now, s…

Old thread, but something I wanted to note: ‘client-ip’ works when hosting locally with netlify dev from the CLI. In that case, though, ’ x-nf-client-connection-ip’ does not. However, once deployed to web, ‘client-ip’ does not work and ’ x-nf-client-connection-ip’ does. Here is my function: import…

Is the "Client-IP" header going to be supported long term?

Support

luke Split this topic July 16, 2021, 1:47am 13

2 posts were split to a new topic: Seeing inconsistency with client-ip: headers in HTTP request proxied from Netlify

Topic		Replies	Views
Upcoming change: Stripping exposed Netlify headers from function and proxy requests Updates lambda-functions , proxying	3	2085	March 14, 2022
Supporting a header with "-Host" as suffix rather than "-Ip"? Features headers , feature-request	2	818	June 15, 2023
Seeing inconsistency with `client-ip:` headers in HTTP request proxied from Netlify Support proxying	3	1580	July 16, 2021
Reverse proxy - how to forward client IP address to Netlify Support netlify-analytics , proxying , redirects	7	2849	April 13, 2023
Proxying services with forwarding client IPs Support redirects	6	3361	September 24, 2020

Is the "Client-IP" header going to be supported long term?

Related topics