You need to
before you can comment on or make changes to this bug.
the server doesn't even get hit, as far as i've observed. This doesn't happen every time, but it happens with at least even odds. I've observed it in the shipping version of Safari 2, the nightly build of WebKit, and the beta of Safari 3. It's quite easy to reproduce, and it's easy to observe, since a submission that should take seconds just hangs and hangs. I'm running Apache 2.x on OS X 10.4.9
Thanks for the bug report, Michael! Does it matter whether you loaded the page with the form using 127.0.0.1 versus localhost? Are you connected to the Internet (or a LAN) when this happens?
Are you actually selecting a file to be submitted, or are you leaving the file input blank? If selecting a file, what type of file is it?
What exact version of Apache are you using (since Apache 2.x didn't come with OS X 10.4.9)? Did you compile it from source, or are you use a precompiled distribution?
i always connect to 127.0.0.1, rather than localhost, but i'll try localhost going forward to see if this persists. I am generally connected to a Lan (wifi) when this happens.
The issue only happens when i have selected a file. If i just submit data, i never see the problem. The type of file doesn't seem to matter. It's happened most recently with PDF and CSV files.
Now that i've submitted this bug, of course, the issue doesn't seem to be as reliably reproduced, but it is still there, i'm sure of it.
I compiled Apache myself. Tthe httpd -V output is below. However, it should be noted that when this problem occurs, the server never gets the request. Even putting a PHP "die()" at the top of the file receiving the upload produces no results when the bug happens.
Server version: Apache/2.2.3
Server built: Oct 30 2006 23:55:59
Server's Module Magic Number: 20051115:3
Server loaded: APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Server MPM: Prefork
forked: yes (variable process count)
Server compiled with....
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
Could you please attach samples of WebKit and Apache when this happens? You can take a sample with Applications/Utilities/Activity Monitor.app.
I just checking for the first time this site looking for upload bugs.
I remarked that particular bug since Safari 2 and still see it in Safari 3 and WebKit (at least until r25410).
I'm under MacOSX.4.10. I'm effectively almost all time connected thru AirPort.
I do not remember I that bug appears when uploading to not localhost.
I got the impression (sorry, not very scientific) the the problem arises every around 20 uploads.
The next time this happens, please run the following commands:
% sample Safari 10 10
% sample httpd 10 10
Note that you may also use Activty Monitor to take samples.
Also note that since Apache is multi-threaded, you may need to run something like "ps auwwx | grep httpd" to find the correct process ID (PID) to use with sample:
% sample PID 10 10
After doing this, please attach the sample output files created in /tmp/ to this bug.
BTW, this sounds like it may be a duplicate of Bug 5760.
After re-reading Bug 5760 Comment #38, this is almost certainly a duplicate of that bug.
There is no need to run sample(1) per Comment #5.
*** This bug has been marked as a duplicate of 5760 ***
(In reply to comment #7)
> After re-reading Bug 5760 Comment #38, this is almost certainly a duplicate of
> that bug.
> There is no need to run sample(1) per Comment #5.
> *** This bug has been marked as a duplicate of 5760 ***
I agree, it sounds very much the same bug.
From #41 of bug 6760, do I understand correctly that there is actually no work around to this bug ?
(In reply to comment #8)
> I agree, it sounds very much the same bug.
> From #41 of bug 6760, do I understand correctly that there is actually no work
> around to this bug ?
The only work-around that I can think of is to move the server off the local machine so that you're going over the network instead of hitting it locally. I'm not positive, but I think the bug occurs when you're using localhost, 127.0.0.1, an IP address bound to an ethernet port or wireless connection, or the hostname associated with that bound IP address.
It's rather unfortunate that this hasn't really been fixed yet.