[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
LYNX-DEV Re: FTP & socks probably needs PASV or else not SHORTENED_RBIND
From: |
Foteos Macrides |
Subject: |
LYNX-DEV Re: FTP & socks probably needs PASV or else not SHORTENED_RBIND |
Date: |
Thu, 14 Nov 1996 15:56:34 -0500 (EST) |
Tom Zerucha <address@hidden> wrote:
>On Thu, 14 Nov 1996, Foteos Macrides wrote:
>
>> Well, I looked real hard and don't see anything wrong with the
>> code, but can't actually try it, so I may have a "blind" spot to something
>> wrong in it. I do want to get it squared away before my mods are included
>> in the Composite. Perhaps if you re-describe the problem, and a patch
>> versus the lynx2-6mods replacements, to lynx-dev, explaining that it's
>> a quickie fix that might help yield an optimum fix, others using SOCKs
>> might also be able to help.
>
>It is something really obscure since it doesn't affect any other proxies
>or local connections, but except to close misconnections in HTTCP.c I
>don't know of any #ifdef SOCKS enclosing a close.
>
>From my HTTCP.c:
>
>#ifdef SOCKS
> if (socks_flag) {
> status = Rconnect(*s, (struct sockaddr*)&soc_address,
> sizeof(soc_address));
> /*BEGIN KLUDGE*/
> if( status < 0 && SOCKET_ERRNO == EISCONN ) {
> NETCLOSE(*s);
> status = Rconnect(*s, (struct sockaddr*)&soc_address,
> sizeof(soc_address));
> }
> /*END KLUDGE*/
> /* For long Rbind. */
> socks_bind_remoteAddr = soc_address.sin_addr.s_addr;
> } else
>#endif /* SOCKS */
That just means that the socket didn't get closed somewhere
else where it should have been. Are you getting the problem just
for http, or also news and/or gopher (try our gopher server, so I
can see if you are keeping the connection open until it times out
itself)?
I wonder if there's more I inappropriately left out of the
hookless mods set. I'll try to compare them more carefully. Do
you have the problem when you swap in the four C modules from
lynx2-6ssleay.zip?
>> There was a lynx-dev message today, or last night, from someone
>> having ftp problems, and the setup indicated socks. I tried the ftp URL
>> from here, and had no problems, but without socks. He didn't indicate
>> if he had the problem reliably, i.e., perhaps he just had a network
>> glitch and transmission timeout, but it might be related. What happens
>> for you with ftp (see appended)? He used PORT. Do SOCKs servers
>> require PASV?
>
>They don't *require* it, but then you should avoid the SHORTENED_RBIND.
>[...]
The problem with PASV is that not all ftp servers handle it, but if
ftp can't be made reliable with SOCKS otherwise...
Fote
=========================================================================
Foteos Macrides Worcester Foundation for Biomedical Research
address@hidden 222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- LYNX-DEV Re: FTP & socks probably needs PASV or else not SHORTENED_RBIND,
Foteos Macrides <=