| |
|
|
|
cURL Mailing List Monthly Index Single Mail
curl-and-php Archives
RE: Reading/Writing to the same file via FTP...
From: -Sys Adm- <centralsource_at_hotmail.com>
Date: Fri, 16 Dec 2011 18:37:13 -0500
On Sat, Dec 17, 2011 at 12:19 AM, -Sys Adm- <centralsource_at_hotmail.com> wrote:
> Date: Fri, 16 Dec 2011 12:04:30 +0600
> To: curl-and-php_at_cool.haxx.se
>
> > READ the contents of a file on my FTP server. (Contents of file are only a single number, 0 - 12)
> >
> > {
> > curl_setopt($curl, CURLOPT_HEADER, 0);
> > $data = curl_exec($curl);
> > }
> >
> $fp = fopen($expire, 'r');
> curl_setopt($ch, CURLOPT_UPLOAD, 1);
> $data = curl_errno($ch);
> > }
> Follow: http://twitter.com/shiplu
> http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
--- This makes no sense to me that in my PHP that fopen, fwrite and fclose can work on the same file "on the fly" with a simple ftp connection call, but cURL can not?
The whole reason I'm using cURL is for it's encrypted authentication to the FTP server.
So basically, if I have to create the file locally with fopen on the client's host machine that is executing my PHP, then they can just "capture" that file prior to cURL uploading it back to the FTP server? This is not at all secure for my application.
I was having this done using a simple FTP connection with fopen, fwrite, fclose, but obviously ftp streams the username:password in clear text... again, the whole reason to use cURL.
Surely there must be a way once I have the "captured" file contents within cURL to overwrite that data "on the fly" and close the file back. With nothing being created locally....
SysAdm
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php
_______________________________________________
Date: Sat, 17 Dec 2011 04:01:31 +0800
Write it to php://memory, then pass it to CURLOPT_INFILE as a stream.http://php.net/manual/en/wrappers.php.php
____________________________
Thanks Liu Shan Shui for verifying what I suspected...
I was "assuming" cURL with just FTP access was encrypting the data transit automatically, no need for FTPS or .pem files, or other "handshake" files needed. I guess I was wrong...
Seems like that would be the next industry standard if someone wrote a lib that "encased" a username:password along transit over HTTP using a simple call... without all the HTTPS, FTPS, needing static IP, etc... etc... hassles...
I ended up going HTTPS, with .htaccess username:password "handshake", then I just used the good old fopen, fwrite, and fclose technique.
Consider this thread SOLVED!
Thanks for everyone's input and ideas....
SysAdm
_______________________________________________
These mail archives are generated by hypermail. |
Page updated November 12, 2010.
web site info