The Problem is, that although I've read (in some old Forums, 2003 and earlier), that there is no DELETE (DELE) through SQUID possible, it works - by me in 2.5 STABLE5 and STABLE 12. I have made with ethereal a dump of network traffic, there are: Client->SQUID HTTP-Request DELE Filename SQUID->FTP FTP-Request DELE Filename FTP-> SQUID FTP-Response File Filename deleted And the file ist really deleted Important: works only with "HTTP CONNECT" Client-Method, neither with "HTTP-Proxy with FTP-Support" (TotalCommander - Response auf DELETE - "Not implemented"), nor anything else. I make now Doku for a software, which also should delete some files through Proxy(SQUID), so I need to know, if it is oficially implemented, if there are any limitations an so on. Thanks for the help EK -----Original Message----- From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Thursday, February 23, 2006 3:40 PM To: Eugen Kraynovych Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: FTP Commands mån 2006-02-20 klockan 15:15 +0100 skrev Eugen Kraynovych: > Does anybody here have a full list of FTP commands, which SQUID 2.5 can > (for instance 2.5Stable12; PUT, GET, DELE etc.)? The same for SQUID 3? Squid acts as a HTTP->FTP gateway on requests for ftp:// URLS. The currently supported HTTP methods on ftp:// URLs are: GET PUT HEAD which gets translated to suitable FTP commands by Squid as per the guidelines outlined for ftp:// URLs in RFC1738 section 3.2. GET is used both for file retreival and directory listings. Binary and Ascii file retreival is supported. If no explicit format is requested Squid guesses using it's mime.conf table which tells Squid both the ftp transfer mode to use and content-type to assign to the reply. Explicit requests for ascii or binary uses text/plain or application/octet-stream respectively for the content-type. Directory listings uses LIST or NLST depending on the format type specifier in the URL. Requests without an explicit format uses LIST, while explicit requests for directory format uses NLST. PUT in addition to storing files using STOR it also automatically creates directories with MKD if needed. Or only creates directories if the URL ends in / and the content-length is 0. If the URL ends in / and content-length > 0 then STOU is used instead of STOR allowing the FTP server to assign a suitable file name to the uploaded content. GET uses REST is the request is a range for the remainder of the file. Support could be added for more HTTP methods such as DELETE mapped to DELE/RMD but nobody has shown any interest in this. Regards Henrik
