MantisBT - Xdebug
View Issue Details
0001533XdebugFeature/Change requestpublic2018-03-07 19:472018-10-19 01:50
0001533: Add ability to override xdebug.remote_timeout per request
We'd like to use xdebug.remote_autostart=1 and xdebug.remote_connect_back=1 to simplify life for our developers. Unfortunately sometimes our overseas developers with high latency need to debug against US servers which would require a high xdebug.remote_timeout setting. This, unfortunately, would negatively impact non-debugging users like QA and PM.

What would be greats is the ability to override for xdebug.remote_timeout per request using something like the xdebug cookie in the request payload. Then the only time the cookie would be necessary is for those few times when we specifically need to support high latency.

- Debugging locally wouldn't need a cookie anymore
- Non-debugging requests wouldn't be severely impacted
- Remote debuggers could override the timeout with their cookie

Thanks for your consideration
No tags attached.
Issue History
2018-03-07 19:47dwilksNew Issue
2018-10-19 00:45derickNote Added: 0004704
2018-10-19 00:45derickAssigned To => derick
2018-10-19 00:45derickStatusnew => feedback
2018-10-19 01:50dwilksNote Added: 0004707
2018-10-19 01:50dwilksStatusfeedback => assigned

2018-10-19 00:45   
I can change this, but I am wondering why you think it would negatively
impact non-debugger users to have a high latency. A well configured TCP/IP stack
should normally instantly return if there is no bound socket to listen. Are you
actively seeing this problem with high latency configured?
2018-10-19 01:50   
Yes. Our (US) remote teams (India/Romania) have been forced to continue to use the debug proxy configuration due to the latency of the network. We can't set remote_timeout too much higher or remote QA (which will never have debuggers) end up complaining about performance.