[xdebug-general] Re: Setting the XDebug Session cookie within a browser.

Derick Rethans <derick[@]xdebug.org> wrote on 23/10/2007 18:18:12:

> On Tue, 23 Oct 2007, Dave Kelsey wrote:
>
> > xdebug-general-bounce[@]lists.xdebug.org wrote on 23/10/2007 16:17:41:
> >
> > > On 23 Oct 2007, at 13:48, Dave Kelsey wrote:
> > >
> > > > Is it possible to get the cookie sent to the browser as soon as
> > > > the script has started executing ? or does this already happen but

> > > > IE doesn't store it until the request completes maybe ?
> > >
> > > I think PHP is to blame here. It usually delays sending of headers
> > > until a script has ended, at which point it sends everything in one
> > > go. You can force it to flush output using flush(). You might also
> > > look into session_write_close(), and the various output buffering
> > > options in php.ini. Further upstream, mod_deflate/mod_gzip can also
> > > delay output until script completion.
> >
> > Unfortunately I don't have control over the script being debugged. I
> > suspect that xdebug cannot help here either as it probably appends the

> > cookie to the current executing php script header response (based on
> > the info you provided).
>
> Yes, that's correct... there is nothing else I can really do here.
> However, then the _GET parameter is present, Xdebug should still start
> the debug session, even though the cookie isn't actually set.
>
> regards,
> Derick
>
> --
> Like Xdebug? Send a postcard:
http://derickrethans.nl/xdebug_2_released.php
> Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org

Hi Derick,
I am not sure just how much of an issue it would be. I am trying to go
over
scenarios where multisession debugging would be useful. An example would
be
an html file that invokes multiple concurrent requests on a server that in
turn executes php code that you want to debug. So long as you are
debugging
the original script, then the cookie should go to the other requests.
My initial testing of this was to start a script being debugged, and while
it
was being debugged, open another browser window and invoke another script
(which didn't get debugged) but I have doubts as to whether this kind of
scenario
would be a common debugging scenario so may not be worth worrying about.

Cheers

Dave Kelsey

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Tue Oct 23 2007 - 19:36:09 BST