www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Villy Kruse <...@pharmapartners.nl>
Subject mod_proxy/6268: proxy_ftp.c fails with some servers -- the communication hangs.
Date Sun, 02 Jul 2000 14:15:25 GMT

>Number:         6268
>Category:       mod_proxy
>Synopsis:       proxy_ftp.c fails with some servers -- the communication hangs.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Jul 02 07:20:01 PDT 2000
>Originator:     vek@pharmapartners.nl
>Release:        1.3.12
Linux redhat 5.1
Some FTP server will not send anything on the FTP control channel before
the data channel has been closed by the server after a file transfer.

On these servers the transfer will not complete properly and the process
will be waiting for input on the FTP control channel forever or until killed.


The site ftp://ftp.nluug.nl is one such site which gives problems when using
apache as a proxy server.  I don't know what server they are running.

Unix servers running wu_ftpd does not have any problem.
Move  ap_bclose(data) to the point right after ap_proxy_send_fb or
send_dir in proxy_ftp.c before the status code is requested after the
file transfer is complete.  This has fixed the problem for me.
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message