Would the xdebug.client_discovery_header (https://xdebug.org/docs/step_debug#client_discovery_header) not work here?

Note: Setting names have changed in Xdebug 3.

In my case, I need to check 2 headers. client_discovery_header only allows set one.

Right, but after Xdebug can't find the client_discovery_header one, it will fall back REMOTE_ADDR.

It falls back in HTTP_X_FORWARDED_FOR and then REMOTE_ADDR, but my prioritory & sequence is other.

Specifically:

• CUSTOM_HEADER_A
• REMOTE_ADDR

So, in my case, i need to set a list of headers (i need to skip HTTP_X_FORWARDED_FOR).

It's the same as:

• CUSTOM_HEADER_A
• CUSTOM_HEADER_B

https://github.com/xdebug/xdebug/pull/841

If someone upgraded to xdebug 3.2 and was using client_discovery_header you have to change it to:

xdebug.client_discovery_header="YOUR_CURRENT_VALUE,HTTP_X_FORWARDED_FOR,REMOTE_ADDR"

if you want the same behavior