On Tue, May 9, 2006 12:14 pm, Rolf Wouters wrote:
>
>>> The script behind the request does the following:
>> Also, if the script terminated and Apache sent a non-200 return
>> code,
>> then the browser "knows" it never got the real page, and may be
>> trying
>> to help you by getting the true page
I don't think it's a timeout issue on the server-side, because I've
already tried setting MAX_EXECUTION_TIME and MAX_INPUT_TIME to
extremly
high values, and got the same result (i.e. the blank page).
By setting them to extremly low values I was able to verify the
app/script/server 's behaviour w
The script behind the request does the following:
- delete some files
- copy files from dir A to dir B
- read some data from a database and generates some XML-files
(i.e. a basic "publish" procedure)
The problem isn't the script itself, nor the server. I know this,
because the same code is b
Do you have short open tags allowed in this server setting?
why not just do
Yes, short open tags are allowed on this server. As mentioned before,
all instances of this app are running on the same server, using the same
configuration etc. Differences between the problem app and the other
Do you have short open tags allowed in this server setting?
why not just do
Rolf Wouters wrote:
>
>> I know I used to have an issue with some of that type of stuff, but I
>> also went in and did an output buffering at the beginning of the script,
>> ran everything, then output the buffer. Th
I know I used to have an issue with some of that type of stuff, but I
also went in and did an output buffering at the beginning of the script,
ran everything, then output the buffer. That helped me to clear it up.
One of the pieces might be outputting something you just aren't seeing
yet...
Al
On Mon, May 8, 2006 4:49 am, Rolf Wouters wrote:
> I don't think it's a timeout issue on the server-side, because I've
> already tried setting MAX_EXECUTION_TIME and MAX_INPUT_TIME to
> extremly
> high values, and got the same result (i.e. the blank page).
> By setting them to extremly low values I
On Mon, May 8, 2006 4:09 am, Rolf Wouters wrote:
> The blank page. It shouldn't be there, and not when the request is
> still running. Or am I mistaken in thinking that the browser should
> wait with displaying _anything_ before it becomes the result-page from
> the server.
This is definitely wr
On Mon, May 8, 2006 3:41 am, Rolf Wouters wrote:
> I'm having some strange behaviour in a PHP4 app I'm working on.
>
> When I send my request to the server, it returns a blank page to me
> within ca. 40 sec. On the server itself, my request is still being
> handled.
It is possible that you are ma
Break it up into sections and have it output the per/section pieces.
You could do iframes or something so that it all looks like a single
page, or split it up as delete files, upload files, create XML, flush DB
or whatever you are doing. I know it is not pretty, but getting it to
clear up is the p
One thing I forgot... Thanks for taking the time and helping me out
with this problem, I should have said that a little bit earlier, but I
hope I'm not to late yet :-)
Greetz
Rolf
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
BTW, would a timeout explain why the browser wants to repost the request
when I trie to view the source-code of the blank-page?
I think that's a firefox thing.. does the same thing happen in IE?
Yes, this also happens IE, but IE doesn't show a blank page, instead it
show me a "Page cannot be
>> We're talking about multiple copy operations. The first one copies 230
>> files (approx. 40mb) and the second one copies about 2200 files
>> (195mb). Most files are under 400kb a piece.
>
> Time how long it takes you to manually copy that amount of data.
Tried the flush() calls in between dif
> I'm guessing it's just a timeout issue - "maximum execution time
> exceeded" type thing - check your php or apache error logs and see
> what that tells you.. if nothing shows up, turn log_errors on, restart
> apache and see what you get.
I don't think it's a timeout issue on the server-side, b
> I'm guessing it's just a timeout issue - "maximum execution time
> exceeded" type thing - check your php or apache error logs and see
> what that tells you.. if nothing shows up, turn log_errors on, restart
> apache and see what you get.
I don't think it's a timeout issue on the server-side, bec
Chris wrote:
Rolf Wouters wrote:
Chris wrote:
Rolf Wouters wrote:
Hello everybody
I'm having some strange behaviour in a PHP4 app I'm working on.
When I send my request to the server, it returns a blank page to me
within ca. 40 sec. On the server itself, my request is still being
handled
Rolf Wouters wrote:
Chris wrote:
Rolf Wouters wrote:
Hello everybody
I'm having some strange behaviour in a PHP4 app I'm working on.
When I send my request to the server, it returns a blank page to me
within ca. 40 sec. On the server itself, my request is still being
handled.
What exac
Rolf Wouters wrote:
Hello everybody
I'm having some strange behaviour in a PHP4 app I'm working on.
When I send my request to the server, it returns a blank page to me
within ca. 40 sec. On the server itself, my request is still being
handled.
What exactly do you want help with? The blank p
Chris wrote:
Rolf Wouters wrote:
Hello everybody
I'm having some strange behaviour in a PHP4 app I'm working on.
When I send my request to the server, it returns a blank page to me
within ca. 40 sec. On the server itself, my request is still being
handled.
What exactly do you want help wit
Hello everybody
I'm having some strange behaviour in a PHP4 app I'm working on.
When I send my request to the server, it returns a blank page to me
within ca. 40 sec. On the server itself, my request is still being handled.
The script behind the request does the following:
- delete some files
20 matches
Mail list logo
