> PUT is raw (AFAIK)
That sounds good. Have you any link to a basicly methode description? This
is a really new methode for me but sounds better than http upload btw.
resume function is not bad.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsu
On 8/8/08, Per Jessen <[EMAIL PROTECTED]> wrote:
> Same as POST then :-) (except for the resume bit).
>
> I still don't see much of a difference. It doesn't matter much to me,
> I'd just like to understand what the real difference is. Maybe I need
> to go and read RFC2616.
I'm all for using ex
mike wrote:
> On 8/8/08, Andrew Ballard <[EMAIL PROTECTED]> wrote:
>
>> I've not had to upload such large files over HTTP, so forgive my
>> ignorance, but on the request end isn't the only difference between
>> PUT and POST the verb used in the request (and the intent of the
>> operation)? What c
On 8/8/08, Andrew Ballard <[EMAIL PROTECTED]> wrote:
> I've not had to upload such large files over HTTP, so forgive my
> ignorance, but on the request end isn't the only difference between
> PUT and POST the verb used in the request (and the intent of the
> operation)? What can you do with PUT th
On Fri, Aug 8, 2008 at 1:08 PM, mike <[EMAIL PROTECTED]> wrote:
> On 8/8/08, Luke <[EMAIL PROTECTED]> wrote:
>> Is a 1.9 gb file upload even sustainable on even a fairly small scale web
>> application? Maybe you could implement FTP if you trust the people that want
>> to upload the file.
>
> This i
On 8/8/08, Luke <[EMAIL PROTECTED]> wrote:
> Is a 1.9 gb file upload even sustainable on even a fairly small scale web
> application? Maybe you could implement FTP if you trust the people that want
> to upload the file.
This is why I am pushing for people to use PUT.
Still over HTTP, uploaders ca
Andrew write the answer:
-1149239296 Bytes is indiz for to big.
This time I had set the upload_file_size and post_max_size to 3000Mb
each, which probably didn't work. When I tried the 1900Mb file again I
got this error:
[Fri Aug 08 16:57:28 2008] [error] [client 192.168.2.113] PHP Warning:
POST
Andrew Ballard wrote:
>> This time I had set the upload_file_size and post_max_size to 3000Mb
>> each, which probably didn't work. When I tried the 1900Mb file again
>> I got this error:
>>
>> [Fri Aug 08 16:57:28 2008] [error] [client 192.168.2.113] PHP
>> [Warning:
>> POST Content-Length of 199
On Fri, Aug 8, 2008 at 11:14 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
> Per Jessen wrote:
>
>> Tom wrote:
>>
>>> Practical i implement a robust filebase in my new gamer portal and
>>> go to max. at upload values. If the users make a big upload, it
>>> should be stable. I think, later (after relea
Per Jessen wrote:
> Tom wrote:
>
>> Practical i implement a robust filebase in my new gamer portal and
>> go to max. at upload values. If the users make a big upload, it
>> should be stable. I think, later (after release) i will enhance it
>> with a ftp port. But not yet.
>>
>> Here you can see
Tom wrote:
> Practical i implement a robust filebase in my new gamer portal and go
> to max. at upload values. If the users make a big upload, it should be
> stable. I think, later (after release) i will enhance it with a ftp
> port. But not yet.
>
> Here you can see, what i have in filebase, bu
Per Jessen wrote:
How about if I upload a 1Gb file to a webserver on a machine that only
has 256Mb memory - would you say that's impossible?
/Per Jessen, Zürich
In my experience that would the correct.
--
Jim Lucas
"Some men are born to greatness, some achieve greatness,
and s
Is a 1.9 gb file upload even sustainable on even a fairly small scale
web application? Maybe you could implement FTP if you trust the people
that want to upload the file.
Luke Slater
Lead Developer
NuVoo
On 9 Aug 2008, at 14:52, "Tom" <[EMAIL PROTECTED]> wrote:
Practical i implement a robu
Practical i implement a robust filebase in my new gamer portal and go to
max. at upload values. If the users make a big upload, it should be stable.
I think, later (after release) i will enhance it with a ftp port. But not
yet.
Here you can see, what i have in filebase, but a 1.9 GB upload fail
Tom wrote:
> Hi Per,
>
> Execution Time ist set to 72000, i learned to set it not to low for
> tests
> :-)
> I learned also the last days many things about the php.ini. Many
> changes affect later, its mostly for me a trial and error thing and
> results in much phenomenon.
>
> At moment its okay
Hi Per,
Execution Time ist set to 72000, i learned to set it not to low for tests
:-)
I learned also the last days many things about the php.ini. Many changes
affect later, its mostly for me a trial and error thing and results in much
phenomenon.
At moment its okay, i can upload 1.2 Gb, no pro
Per Jessen wrote:
> Jim Lucas wrote:
>
>> I have never seen a case where Apache has stored the file on the file
>> system. In my past experience it has always held the file in memory,
>> therefor limited to the max physical memory that was install, minus a
>> little for other things.
>
> Well, I
Tom wrote:
> Hi Per,
>
> your result is on a suse 8.2 ?
> hmm, i don't know the reason why my suse 10.2 machines do that
> failure. My limits for for post_max_size and upload_max_size is both
> 1500M.
>
> Greets & thanx, Tom
Tom,
check your maximum PHP execution time. I've just done some tes
Am Freitag, den 08.08.2008, 09:00 +0100 schrieb Luke:
> Maybe there is some configuration in the server somewhere causing it
> to incorrectly use the tmp?
normla config php.ini
; Whether to allow HTTP file uploads.
file_uploads = On
; Temporary directory for HTTP uploaded files (will use syste
Maybe there is some configuration in the server somewhere causing it
to incorrectly use the tmp?
Luke Slater
On 8 Aug 2008, at 08:48, Torsten Rosenberger <[EMAIL PROTECTED]>
wrote:
Hello
on a linux system (Suese 10.2) with 1 GB memory its not possible to
upload
via http a 1 Gb File. T
Hello
> on a linux system (Suese 10.2) with 1 GB memory its not possible to upload
> via http a 1 Gb File. Thats no limit problem on my php config. i can look
> the mem stats when uploading and the growing tmp file. If the temp file has
> 900 MB, Main Memory free is 0 and the script aborts an
Luke wrote:
> I think the sentiment is that you can't fit all of the file in the
> memory at once
>
Which would be absolutely true, but irrelevant - the question is whether
that would prevent me from uploading it? That is the problem Tom seems
to be having.
/Per Jessen, Zürich
--
PHP Gener
I think the sentiment is that you can't fit all of the file in the
memory at once
Luke Slater
On 8 Aug 2008, at 07:59, Per Jessen <[EMAIL PROTECTED]> wrote:
Jim Lucas wrote:
What Apache starts, it reads the PHP memory limits in to the running
Apache process. When you try and upload a file
Jim Lucas wrote:
> What Apache starts, it reads the PHP memory limits in to the running
> Apache process. When you try and upload a file, it is a straight HTTP
> upload. PHP plays no part in the actual upload, except for the upload
> limits set in place by the php settings found in the php.ini o
Simple answer is yes. But others might argue this answer.
Luke wrote:
Tom's machine only has 1 GB of physical memory doesn't it? Could that be the
problem?
2008/8/7 Jim Lucas <[EMAIL PROTECTED]>
Tom wrote:
Hi,
on a linux system (Suese 10.2) with 1 GB memory its not possible to upload
via
Tom's machine only has 1 GB of physical memory doesn't it? Could that be the
problem?
2008/8/7 Jim Lucas <[EMAIL PROTECTED]>
> Tom wrote:
>
>> Hi,
>>
>> on a linux system (Suese 10.2) with 1 GB memory its not possible to upload
>> via http a 1 Gb File. Thats no limit problem on my php config. i
Tom wrote:
Hi,
on a linux system (Suese 10.2) with 1 GB memory its not possible to upload
via http a 1 Gb File. Thats no limit problem on my php config. i can look
the mem stats when uploading and the growing tmp file. If the temp file has
900 MB, Main Memory free is 0 and the script aborts
Hi Per,
your result is on a suse 8.2 ?
hmm, i don't know the reason why my suse 10.2 machines do that failure.
My limits for for post_max_size and upload_max_size is both 1500M.
Greets & thanx, Tom
"Per Jessen" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
Tom wrote:
> i
Tom wrote:
> i use ext3
> Im realy on no limit. destination ist /tmp and is fairly empty.
> The question is now, if cache full => must hypothetical swap used?
> ok, im glad to see your result.
No, high utilization of file system cache will not cause any swapping -
file system caching uses whatev
i use ext3
Im realy on no limit. destination ist /tmp and is fairly empty.
The question is now, if cache full => must hypothetical swap used?
ok, im glad to see your result.
"Per Jessen" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
Tom wrote:
>>Ah, so it's not PHP and it'
Tom wrote:
>>Ah, so it's not PHP and it's not apache using up your memory - it's
>>your
>>filesystem cache. Check how many files you have in the tmp directory
>>and the destination directory.
>
> Okay, thats light in the darkness. But i don't have any idea what i
> can do here. tmp is empty.
>
>Ah, so it's not PHP and it's not apache using up your memory - it's your
>filesystem cache. Check how many files you have in the tmp directory
>and the destination directory.
Okay, thats light in the darkness. But i don't have any idea what i can do
here. tmp is empty.
Look at the first entry,
Tom wrote:
> With what linux BS have you tested?
It was an older SUSE Linux 8.2. But the OS shouldn't matter - maybe the
PHP release and maybe the apache ditto.
> No, it isn't the apaches job/problem.
> I do nothing with the file. Looking for $_FILES Varables and then
> move_uploaded_file.
Th
With what linux BS have you tested?
No, it isn't the apaches job/problem.
I do nothing with the file. Looking for $_FILES Varables and then
move_uploaded_file.
But i said it before, the problem is not at this point.
If i upload the file and watch memory with vmstat, free is going 0, cache is
goi
Tom wrote:
> hmm, memory buying is okay, not the final solution. I think php design
> fault on this function. It's not comprehensible why php use such a
> lot main memory for an upload.
Well, PHP doesn't - the upload is apaches job. Once the file is
uploaded, PHP is invoked to process it. You d
Tom wrote:
> But on a big website with upload enabled and 30 users upload simultan
> a 20 MB File, they lost the upload while php hold all in memory/Cache
> and swap is not used. I don't understand why php write the upload
> chunck for chunck (i can look this) in upload temp file AND holds the
>
hmm, memory buying is okay, not the final solution. I think php design fault
on this function. It's not comprehensible why php use such a lot main
memory for an upload.
""Richard Heyes"" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
> Well, you lost me right about... Well
Well, you lost me right about... Well when you started. But memory is
cheap...:-/
--
Richard Heyes
http://www.phpguru.org
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
smaller files is no problem. The error occoured, if the uploaded File is
bigger than the installed main memory.
Ok, i know that http ist not designed for big uploads. But on a big website
with upload enabled and 30 users upload simultan a 20 MB File, they lost the
upload while php hold all in m
> No Apache limit, enough diskspace, no permission problem.
> Fact is: During upload looking at main memory, goes to 0 and if 0 uploadet
> tmp File was deleted and no error occur.
>
> It was great, if anybody can test such a upload. The uploaded File musst be
> greater as main memory. While teh ulo
No Apache limit, enough diskspace, no permission problem.
Fact is: During upload looking at main memory, goes to 0 and if 0 uploadet
tmp File was deleted and no error occur.
It was great, if anybody can test such a upload. The uploaded File musst be
greater as main memory. While teh uload is run
Tom wrote:
> No, ist'not a php limit. The upload is written in main memory, if i
> look with vmstat, free is going to 0 and the php upload breaks at 0
> bytes free. Nothing swap used. Any other ideas?
>
Interesting problem - maybe an apache limit? Lack of diskspace?
Permissions? Which error d
No, ist'not a php limit. The upload is written in main memory, if i look
with vmstat, free is going to 0 and the php upload breaks at 0 bytes free.
Nothing swap used. Any other ideas?
"Per Jessen" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
Tom wrote:
> Hi,
>
> on a linu
Tom wrote:
> Hi,
>
> on a linux system (Suese 10.2) with 1 GB memory its not possible to
> upload via http a 1 Gb File. Thats no limit problem on my php
> config. i can look the mem stats when uploading and the growing tmp
> file. If the temp file has 900 MB, Main Memory free is 0 and the
> scr
Hi,
on a linux system (Suese 10.2) with 1 GB memory its not possible to upload
via http a 1 Gb File. Thats no limit problem on my php config. i can look
the mem stats when uploading and the growing tmp file. If the temp file has
900 MB, Main Memory free is 0 and the script aborts and php dele
Angelo Zanetti wrote:
thanks, but Im sure there is something that is messing up the file
permissions that I can change before the upload, instead of trying to
cure the problem by setting the chmod of the file after its uplaoded
Check the following things:
1. umask settings on the director
The remote PHP machine maybe forces the files to
change their permission when uploaded. This would be
security measure. And I think that if this is the
case, you won't be able to change the permissions.
===
Hristo Yankov, Developer at Portellus, Inc.
ICQ - 1
Use chmod() on the uploaded file.
===
Hristo Yankov, Developer at Portellus, Inc.
ICQ - 191445567
Yahoo! - yankov_hristo
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http
thanks, but Im sure there is something that is messing up the file
permissions that I can change before the upload, instead of trying to
cure the problem by setting the chmod of the file after its uplaoded
Hristo Yankov wrote:
Use chmod() on the uploaded file.
=
Hi all.
I've got a PHP script which does file uploads.
the files get uploaded fine but I see that the permission of the files are:
600
IE: Owner read and write.
In order for me to use the files, I would have to set the permissions on
each file, now for best practise would I set the permissio
I have a problem uploading files with PHP which has me stumped! I am unable
to successfully upload files. My simple test script is as follows:
File successfully upload." ;
print "Try again?" ;
}
else
{
print <<< __RAWHTML__
Filename:
__RAWHTML__;
print
sto cercando di scrivere una pagina per l'upload di file, ho copiato dei sorgenti ma
non funzionano. queste sono le pagine:
-form.html
upload.php---
---
non carica nulla e non restituisce alcun input, se cerco di visualizzare l'html, dal
max_execution_time does not affect file uploads. Php script and thus
also the timer starts after the upload is finished. max_input_time might
influence it as it is the time allowed for the browser to post the data.
Justin French wrote:
See these three directives in php.ini:
max_execution_time =
On Thursday, October 30, 2003, at 01:40 PM, Louie Miranda wrote:
Im made a file upload program. I limit my php.ini to accept only 5mb
but i
told on my website that it is 2mb only. Now here's my problem.
I only upload a 1.5mb and a 1.7mb file when ever i submit it the
browser
displays
"the pag
Hello,
Im made a file upload program. I limit my php.ini to accept only 5mb but i
told on my website that it is 2mb only. Now here's my problem.
I only upload a 1.5mb and a 1.7mb file when ever i submit it the browser
displays
"the page cannot be displayed" but when ever i upload a file lower th
55 matches
Mail list logo
