That would be a case to write in a separate logging function then. But for remote IP, filename, result code, and I believe size, the default Apache log has all of these.
Also, why would you write a HTTP CGI for FTP? Why not just send the file out via HTTP, this alleviates the overhead needed for FTP. | [reply] |
Having a CGI to go to FTP could be used for load balancing or choosing the FTP server closest to you.
| [reply] |
You can do this with webservers can't you? If you have geographically mirrored content, then you can use HTTP or FTP - it doesn't matter.
That's my $0.02 worth - I am only saying this because it's becoming a popular phrase around here.
| [reply] |