AltME groups: search

Some FTP problems can be bypassed with:
system/schemes/ftp/passive: true
(Don't ask me why!)

We posted the complete source to our FTP client interface, you will 
find the code to handle most of this.

ftp-gadget i guess? http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=ftpgadget-package.r
And  you can try it with the gui first :)

if not, can you make an account to trace and try?

Reichart: Thanks for posting the source code.  Unfortunately, it 
doesn't look like it can be used like the standard FTP protocol in 
Rebol as it is integrated with your GUI.

I downloaded the source code and upon quick inspection, it doesn't 
look like I could use the FTP by entering ftp://user:[pass-:-server], 
but I could be wrong.

Bo, I've done a bit of FTP hacking. Maybe I can find the bug.

does  ftp-gadget work with your server by gui? eg is the ftp-part 
good enough? If not, where can we test against that server?

Bo: Also, I am using FTP in passive mode.

I do not know, if it will help you, but I check the cached connections 
in systems/schemes/ftp/handler/connections for any already closed 
connection before doing an ftp action.

is ftp-gadget still much better  then ftp? looks like  a module with 
gui-callbacks to me. and i spottet the word "async" somewhere.

if all [	

 lock: wait join copy [0:0:0.001] system/schemes/ftp/handler/connections 
 ; problems with closed, but still cached connections
	none? copy lock
] [
	close lock
	remove find system/schemes/ftp/handler/connections lock
]

The problem I'm having is that most FTP transfers work fine, but 
somewhere along the line (say after 50 FTP connections or perhaps 
as many as a couple thousand FTP connections) one of the connections 
hangs up (presumably because the FTP server returned an unexpected 
response, like not being able to open a directory).

I've set up an FTP user for testing on our server called "rebol3" 
with the password "rebol3".  This user has all permissions in its 
sandbox directory.  Feel free to test, but as I said, it may take 
thousands of FTP requests to get one that locks Rebol up.

Volker, I presume that is you connecting to the FTP server.  You 
got two 425 errors from the server the first two times you connected. 
 That's the same part where Rebol was hanging up for me.

And are you sure you don't have bad FTP server?

No.  I may have a bad FTP server, but I am still concerned that Rebol 
would lock up even if the FTP server was bad.

My problem is that I am trying to do a remote backup of a complete 
directory that may contain thousands of files.  On a local area network, 
it always works fine (not using FTP), but when using FTP, it locks 
up seemingly at random.

I'm not certain, but it only seems to happen when backing up when 
part of the path is over wireless.  At least that is where the problem 
was detected and it is also how I've been testing it.  But then I 
noticed that the FTP server gave the 425 error at the same time the 
lockup happened.

I'm doing an open and copy on the source machine and I'm writing 
to the FTP server using 'write/binary/append

What part of the SDK do you want?  The ftp-prot.r file?  I can place 
that on the FTP server under the rebol3 account.

OK.  It's on the FTP server now as prot-ftp.r

you may try my ftp-sync script ftp://rebol3:[rebol3-:-69-:-12-:-157-:-73]/test/ftp-sync-latest.zip 
I never used it in the real life, so maybe it's not perfect as well.

Do I replace the regular prot-ftp.r with this?

no... and I see, the zip is not complete, I uploaded complete script 
to:  ftp://rebol3:[rebol3-:-69-:-12-:-157-:-73]/test/ftp-sync_latest.r

Smooth-Copy has an adjustable wait mechanism built in, but it may 
make the overall length of the transfer too long.  I'll have to put 
some debugging statements in prot-ftp.r to see if I can isolate the 
problem and figure out how to go around it.

Yup, just verified that Rebol always hangs up when the FTP server 
logs a 425 response: "425 Can't open data connection"

I've found THE LINE that Rebol hangs up on when the FTP server returns 
a 425 response.  It is the line with the ;<--- after it below:

	accept-connect: func [port type][
		if not port/locals/passive [
			either port/locals/listen-port [
				if type <> 'new-dir [
					port/sub-port: first port/locals/listen-port ;<---
				]
				close-listen port
				port/locals/listen-port: none
			][
				net-utils/accept-proxy port/sub-port
			]
		]
	]

Obviously, it is in an infinite wait for a listen port that will 
never come.  Can you see any problems if the line were changed to:


if port? lstn-prt: wait [any [system/schemes/ftp/timeout system/schemes/default/timeout 
30] port/locals/listen-port][port/sub-port: lstn-prt]

there should  be a timeout, yes. Would  trigger an error too, how 
 is that done in the right way with ports? Because i do not know 
what this code  does without a port/subport.

what confuses  me, this code runs also in passive  mode?


an idea of mine is to listen on both ports, control and this one. 
if the server sends the 405, its never processed because we dont 
listen there. Should  listen on both ports and still handle commands. 
But do not know what the  right vars are.  Waiting for the skilled 
 ftp-patchers  before examining^^

In limited testing, my patch above (slightly modified to remove typos) 
works.  If the 425 occurs, after a timeout period the patched protocol 
picks up right where it left off.  But yes, I would really like the 
skilled ftp-patchers to take a look at the problem and see if they 
can come up with a better fix.

Are you sure that this happens in passive mode, despite  " if not 
port/locals/passive [  "


I found this line also to be the cause for infinite waiting when 
using ftp with active mode thru a firewall . But activating the passive 
mode eliminated the need for a patch on  my side.

It depends if the particular server supports resume. My batch-downloader 
manages to do resumes from most FTP sites I have tried.

Does it support FTP login?

But FTP might have problems with corporate firewalls, right?

It supports FTP urls. If the url can contain the login details, then 
it should be ok.

Sorry, my first comment above "resumes from most FTP sites" should 
be "HTTP sites". I've not widely tested it with FTP, only with a 
few FTP files Graham was using for his EMR project.

Brian, thanks. I forgot to say that this is a script on XP operating 
system. I have the following line in the target field of a shortcut:

C:\.Alkitab\ftp-backup.r -s allow

But the window still pops up.

C:\Program Files\rebol\view\rebol.exe -s allow C:\.Alkitab\ftp-backup.r
 doesn't work either.

C:\Program Files\rebol\view\rebol.exe C:\.Alkitab\ftp-backup.r -s
  doesn't work either.

OK, I copied rebol to the same directory as the script, and now this 
works:

C:\.Alkitab\rebol.exe ftp-backup.r -s

hi, i would like to know how to open a port with rebol in FTP to 
connect a ISERIES or IBM I or AS400 and execute commande like this 
on  "quote namemft 1" or "cd /" or "quote syscmd call a PGM"

i would like to do it like in dos windows  that the FTP command can 
take a file as input and then execute all commands in that file

Claude you'll have to write your own ftp client

You might be thinking of one of these:
>> first system/schemes

== [self default Finger Whois Daytime SMTP ESMTP POP IMAP HTTP FTP 
NNTP HTTPS]

Was CHMOD ever implemented for the FTP scheme in REBOL 2?

No... or was it with that experimental FTP stuff I did...

SYSTEM/SCHEMES/FTP/PASS is a none of value: none
  set-net ['abc]
  ? system/schemes/ftp/pass
SYSTEM/SCHEMES/FTP/PASS is a string of value: "abc"

the documentation says "The first value is your email address and 
it is used when sending email and connecting to FTP. This value is 
stored in the REBOL system object at: SYSTEM/USER/EMAIL".

I don't think it's a good idea that the ftp password will be set 
to the email address as well, "used when connecting to FTP" maybe 
it should set the user instead

the convention for anonymous FTP is to provide "anonymous" as the 
user and the email address as the password.

You might be able to modify my ftp protocol for R3 to add the SITE 
command so that you can do CHMOD if that's the aim

modify my ftp protocol

 for R2. R3 doesn't have anything like GET-MODES yet, though something 
 is planned.

or you could modify the ftp protocol for r2 to display all the file 
modes sent back by the LIST commands

That might be tricky though, because different FTP servers format 
that information differently. A large portion of the source for FileZilla 
or other FTP clients that have GUIs for file listings is different 
parsers for the file listings of different FTP server software.

IIRC mozilla's ftp server code is like 1MB of source code.

practically speaking though if you only have the one ftp server .. 
you only have to do it once

ftp server.... should read   ftp server specific

Practically speaking, there are probably over a hundred different 
FTP server platforms, and the R2 parsing code only supports (hopefully) 
most of them.

It would have been great if the output format of the FTP commands 
had been part of the FTP spec. C'est la vie.

one of the problem is the ftp RFC which changed too many times and 
some older servers which forked between those changes.

Plus the stuff not covered by any of the RFCs at all, like file listing 
formats. There are Windows FTP servers that format their listings 
like DOS DIR listings, Unix servers that actually call ls, etc.

Oops, you wanted FTP, sorry.

I'm a newbie to Rebol. I need to know how to delete a file on my 
website. I tried uploading a file using:

write ftp://user:[pass-:-website-:-com]/myfile.enc myfile.enc


which does not work because of the ['-:-'] in the user name. I tried 
replacing the ['-:-'] with '%40', still did not work. So I tried the 
following which works:

ftp-port: [
	scheme: 'ftp
	host: "ftp.mysite.org"
	port-id: 21
	user: "[user-:-mysite-:-org]"
	pass: "xxxxxxxxxxxxx"
	target: %myfile.enc
]
file: read %myfile.enc
write/binary ftp-port file


So now my file is on my server. My question is - How do I delete 
this file? I see no way to tell the Delete command the name of the 
file on my server so it can delete it. And:

delete ftp://user:[pass-:-website-:-com]/myfile.enc


does not work for the same reason the standard velsion of write does 
not work, because of the ['-:-'] in the user name. Any help much appreciated.

delete [
	scheme: 'ftp
	host: "ftp.mysite.org"
	port-id: 21
	user: "[user-:-mysite-:-org]"
	pass: "xxxxxxxxxxxxx"
	target: %myfile.enc
]

does that work?

Try this http://rebol.wik.is/Protocols/Ftp

See the file attached at the bottom

do %prot-ftp.r

then, do this

delete ftp://user%2540mysite.org:[pass-:-ftp-:-mysite-:-org]/myfile.enc

I had to type that all out very slowly and carefully, long password, 
and I don't use the shell much these days (I'm an old Amigan). YES 
it worked! Thanks Graham. I'll add the guimauve, they do look delicious. 
Help me out much more and end up delivering a feast.


So I imagine I need to include prot-ftp.r in my Rebol programs and 
I'll be able to use the standard way of accessing files on my server? 
Am I right?

Thanks for all the help, this will get me going now.

You can try this .... instead of loading up the ftp protocol, 


 system/schemes/ftp/handler/open-check: [none ["220" "230"] ["USER" 
 dehex port/user] "331" ["PASS" port/pass] "230" "SYST" "*"]

system/schemes/ftp/handler/open-ftp - Is that on windows? I don't 
have anything like that here on linux.

it's open-check .. not open-ftp

? system/schemes/ftp/handler

will show you what resides inside the handler

prot-ftp.r is a file in my home folder. I hope that makes sense. 
Anyway, your code works :)

anyone interested in an SCP based file copy software? this uses SSH 
port, so no need for ftp on the server  :-)  I've already got file 
browsing working.

although the access is slower than ftp, its much more stable.  the 
ssh protocol is much more constistent AFAIK.

I of course use other programming laguages for my work. REBOL is 
mostly useful as a helper for me.

I use it to generate data, parse big files to extract something, 
automated FTP/HTTP/EMAIL jobs, small GUI applications.

In my chat client, I use Allen's parser to create active links for 
http/s ftp etc.

The code that blocks the UI is a ftp file upload, which to the best 
of my knowledge is done synchronously, hence the blocking.

You need an async version of ftp, or spawn another process to do 
this.

Correct me if I'm wrong, but there doesn't seem to be an async ftp 
handler available despite the existing async network ports implemenation.

Correct,there is no async ftp implementation

re: dobeash.com
	- transfer of domain OK
	- ftp of backup content to domain OK
	- http access ... not working ... will investigate

R3 GUI is very important to me as wel
 ... ditto!!!


All these changes appear to have degraded the usability of rebgui 
somewhat

 ... remember that these are development builds, only accessable via 
 SVN. I was hoping to stabalize and "release" by end of this month 
 (September), but the domain issues I've been having have probably 
 pushed that back a month.

In the meantime I re-read port documentation, and try to study http 
scheme, but this is hardly usefull for the community, as I am not 
the one able to bring in e.g. ftp or other scheme anyway :-)

We do have some very specific things that need to be done, such as 
FTP and making other protocols and REBOL/Services (which has been 
ported now). I need to get VID3.4 done, so I can work on GUI and 
graphics.

wouldn't it be good to get pop3, imap, smtp and ftp back to work 
first?

and i have no ftp currently T_T

it's the same reason you can use READ on files, HTTP, FTP, etc.

BrianH: I don't agree to your nor Carl's reasoning towards patches:


1) I use custom patch for URL ftp format, which goes probably anti 
RFC, but is very practical (@, # in username). Putting those things 
into DevBase is nto an option - it would not be accepted

2) As Carl suggested, building custom rebol.exe is not an option 
too, because - I don't want tonnes of various rebol.exes around, 
one adding this thing, another one changing the other thing.

3) This whole thing is not a big deal, I just will have to add do 
%my-init.r into the beginning of each of my scripts, which sucks 
though ...

Pekr.. it's not too practical and safe to use urls with passwords. 
And if you need to connect to ftp with such a user's name, using 
scheme directly should work

Geomol.. because there are people which wants to follow RFC! The 
above Pekr's "patch" is against RFC. One thing is, that you can use 
chars like @ in user name FTP's scheme. and another is that you cannot 
use it in URL. But that's not the topic here. The topic is,that Pekr 
want to modify his system against standarts - then he can use SDK 
and build his own URL handler.

Hm, trying to connect to FTP from my virtual XP kills my router. 
I have to find other way to upload that vector document from r3-alpha...

What do you mean by completness? IMO R3 is more advanced than R2 
already, and we are nearing beta stage =  system architecture is 
in-there, all slots in the right place. Now we need to finish few 
things, for user to be usable as R2 is:


- better console (not necessarily needed, but Windows one is total 
crap and makes experience 40% worse for me)
- fixed call
- network protocols (ftp, pop, smtp, proxy )
- ported DB drivers (done by community hopefully)

- improved parse (needed probably if we want to have DB drivers and 
network drivers done new way, but not necessarily)
- missing CGI mode
- GUI far from beta

as for networking - no, what I had in mind is networking schemes 
- we do have only http 1.1, no proxy, no smtp, no pop3, no ftp, etc

Well, we don't need of specific refinements, cause we can pass a 
block to read (which is converted to a port!).

>> read [scheme: 'ftp host: ... path:... other_data: ....]


The  block format could be used to pass other parameters in a more 
handy way.


>> read [ftp://ftp.rebol.com/matrix.avifile: %movies/matrix.avi]


And the good news, is that it's absolulty possible to have something 
like that now.
We just have to patch the function: system/intrinsic/make-port

Seems to have worked .. managed to upload 32Mb using ftp

So, for hylafax which uses the ftp protocol ... I would have to rewrite 
the whole scheme because the ftp scheme assumed the directory listing 
was always in a certain format etc.

However, FTP directory listings are a different issue, protocol overhead 
that needa a lot of special-case code, as I recall.

Correcting myself about my claim regarding CRLF not sent by REBOL 
built-in protocols : REBOL does send CRLF even if 'newline if used 
as line terminator. A conversion is applied and it becomes CRLF once 
inserted in the port. This automatic conversion (LF=>CRLF) is OS 
independent and is triggered by /lines refinement used on OPEN native 
in root-protocol/open-proto. AFAICT, this behaviour is not documented 
explicitely anywhere. I can just find a few mentions about such conversion 
here : http://www.rebol.com/docs/core23/rebolcore-12.html, but it 
looks like it's related to FTP scheme only (while in fact being the 
default for all schemes relying on OPEN-PROTO).

Only from close friends living in the java world, beyond them, no 
one. I don't expect much from outside REBOL world yet, Cheyenne is 
mainly useful for REBOL programmers. Once it reaches 1.x, Cheyenne 
will have features that would make it more interesting for outsiders 
(like a simple web control panel, web sites and webapp packaging 
in one unique executable, on-demand ready-to-use web application 
loading from our servers: blog, forum, bugtracker,...). I may also 
add a FTP service in a future 1.x version and a lot of other innovating 
new features I have in mind. ;-)

oops, sorry, there is no "pick" in http.
it is in ftp.

Offered by:
	TomBon
Task:

 R3 - Bindings for libcurl - the multiprotocol file transfer library
	http://curl.haxx.se/libcurl/

	C - API  -> http://curl.haxx.se/libcurl/c/allfuncs.html


  libcurl is a free and easy-to-use client-side URL transfer library, 

 supporting DICT, FILE, FTP, FTPS, GOPHER, HTTP, HTTPS, IMAP, IMAPS, 

 LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, TELNET 

 and TFTP. libcurl supports SSL certificates, HTTP POST, HTTP PUT, 

 FTP uploading, HTTP form based upload, proxies, cookies, user+password 

 authentication (Basic, Digest, NTLM, Negotiate, Kerberos), file transfer 
	resume, http proxy tunneling and more!


 libcurl is highly portable, it builds and works identically on numerous 
 platforms, 

 including Solaris, NetBSD, FreeBSD, OpenBSD, Darwin, HPUX, IRIX, 
 AIX, Tru64, Linux, 

 UnixWare, HURD, Windows, Amiga, OS/2, BeOs, Mac OS X, Ultrix, QNX, 
 OpenVMS, RISC OS, 
	Novell NetWare, DOS and more... 

Amount:
	$150
Valid until:
	01.11.2010
Terms:
	PayPal

We will need FTP. That is going to be a pain, but someone has to 
do it.

Henrik .. are you offering to do the ftp protocol?