0000964: Xdebug does not parse X-Forwarded-For

ID	Project	Category	View Status	Date Submitted	Last Update
0000964	Xdebug	Step Debugging	public	2013-07-16 19:07	2017-12-02 16:19

Reporter	mslade	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform	Linux	OS	BU Linux	OS Version	5.0
Product Version	2.2.2
Fixed in Version	2.6.0alpha1

Summary	0000964: Xdebug does not parse X-Forwarded-For
Description	Xdebug uses the X-Forwarded-For header for remote_connect_back but it doesn't parse the header value. It assumes it to be a single IP, so when multiple IPs are included here it results in a malformed hostname. Here is an example from my log file: I: Remote address found, connecting to 168.122.67.172, 168.122.67.172:9000.
Steps To Reproduce	Configure Xdebug with xdebug.remote_connect_back = 1 and xdebug.remote_log writing somewhere you can reach. Issue a request such as curl -H 'X-Forwarded-For: 127.0.0.1, 127.0.0.2' --cookie 'XDEBUG_SESSION=test-case' http://localhost Look at the Xdebug remote log file and note a line such as: I: Remote address found, connecting to 127.0.0.1, 127.0.0.2:9000.
Additional Information	https://en.wikipedia.org/wiki/X-Forwarded-For#Format Note that I tested this against 2.2.2, but it appears to be the same in 2.2.3.
Tags	No tags attached.

Operating System
PHP Version	5.4.0

derick 2013-07-23 10:52 administrator ~0002543	Which one should I use then? The first one to do the callback?

mslade 2013-07-23 16:51 reporter ~0002545	That would be the behavior I expected. The first IP will be the client's actual IP address at the end of the proxy chain.

derick 2017-01-04 11:20 administrator ~0004155	Fixed, through a patch by Steve Easley.