Posted by jwlum on 03/21/06 23:16

I agree that it's most generally a browser/CGI implementation issue,
but I was hoping some fellow PHP travellers had encountered the issue
or could shed some light on why it happens in my simple example.
(That's assuming others can readily reproduce the behavior, which may
not be the case if server settings are the culprit here.)

It's true that I can get around the problem with additional code
overhead. However, I'm hoping for pointers about why this happens at
all, whether it's actually expected behavior, and how caching/HTTP
header info could be coming into play here when the behavior seems to
be controlled by DOM-related activity alone (window.open).

Thanks for the ideas--hoping for others as well,
John

• Next in forum: Re: Forking a PHP process into the background in a web server environment
• Prev in forum: Re: Forking a PHP process into the background in a web server environment
• Thread view: Re: Form fields don't persist after window.open, form submit, browser back

[Reply to this message]