Closed Bug 979268 Opened 10 years ago Closed 10 years ago

Timeout while debugging website in IDE usind Xdebug

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Version:
29 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: gnysek, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36

Steps to reproduce:

I'm using Xdebug and PHP Storm to debug PHP website. Open web page, and have breakpoint set in code. Wait around 1 minute.


Actual results:

Firefox shows "Timeout" error page, like there's no network connection, or no resposne came. I'm more than sure that PHP server didn't stopped since I can still go step by step through code on IDE side.


Expected results:

In previous versions, Firefox was waiting as long, as response came, even when debugging took 20 minutes or longer. Now it cancels request after 1 minute, so I won't see actual response after debuging is finished.
You seem to be saying that this behaviour started recently, but your bug description contains no version information because you used Chrome to report it. Can you give more details about which version worked and which version didn't?
Flags: needinfo?(gnysek)
I'm using Firefox 29.0a2 (Aurora). It was working in previous one 28.0a2
Flags: needinfo?(gnysek)
Component: Untriaged → Networking
Product: Firefox → Core
The same for me, using PHPStorm + XDebug and Firefox 29.0 (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0).
The previous version I used was 28 (with the latest patch) where the problem did not occur.

Thank you!
Steve, is this also expected fallout from bug 947391 ? :-)
Blocks: 947391
Component: Networking → Networking: HTTP
Flags: needinfo?(sworkman)
For me it looks that it's cause of changes in mentioned bug (#947391), cause there is no problem if headers and some html is send to browser and then debuggers stops on breakpoint. Looks that problem occurs only when no content or headers are yet send.
yes - this is related. I think for this use case the best thing to do is just to configure the browser with a higher timeout

goto about:config and set network.http.response.timeout to 65000 (that's in seconds - and it is limited to 16 bits).
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(sworkman)
You need to log in before you can comment on or make changes to this bug.