Hello,

I have some data currently being submitted via the POST method because it is too large to use with GET method submission. I can capture this request in an HTTP proxy like Fiddler. However, I have a problem with a call to one of many php scripts in a session. I would like to track down the specific request in Fiddler and "reissue" the request, but then have PHPEd intercept and help me debug that particular request.

Up until now I've had to rely on work to carve down the request data so I could fit it in a browser URL and break into the debugger that way and hope the bug still happens.

Is there a better way when it comes to debugging php for requests too large for GET and not suitable to run back through a browser to trigger DBG?

Your help is appreciated.

even if you post large data, you can still debug your scripts. In order to do this, you need to supply DBGSESSID to the server. It can be done for example by appending it to the script name in the form target. See other ways explained there http://forum.nusphere.com/howto-run-debug-session-t585.html