MOO Meeting 970305

A summary of the meeting on the MOO, 970305

participants:
 Henrik (Henrik Nordstr=F6m)
 DW (Duane Wessels)
 Luyer (David Luyer)

Most discussion was about ftpput, and how it (or Netscape) works.

ftpput via a proxy, is as one might expect a plain PUT request.

PUT ftp://server/path HTTP/1.0
User-Agent...
=2E..
Content-Length: xxx

data
=2E...

At least Nescape doesn't send a Content-Type header.

My suggestion on how to select ASCII or BINARY is to always do BINARY
unless otherwise specified by ;type=3Da

Luyer and I agreed on that ftpput might be a good task to start with to
get the FTP protocol natively in Squid (no separate ftp process). ftpput
is in many respects much simpler than ftpget, and it shares most of the
protocol part, so that when ftpput is done and tested, then it should be
much simpler to implement ftpget as well.

As a side track from this there was some discussion about PUT and
caching. RFC 2068 has a note on this:

   If the request passes through a cache and the Request-URI identifies
   one or more currently cached entities, those entries should be
   treated as stale. Responses to this method are not cachable.

The only thing that is a bit unclear is if objects are stale even if the
PUT request fails.

Then there was some discussion about URN (URI above is either a URL or a
URN), but it seems that URN not yet formalized and as such it has no
implication for squid (it is more as a name for something to be later
on).

---
This is my personal notes from the meeting. Corrections/additions are
welcome.