[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r14262 - trunk/subversion/mod_dav_svn

From: <kfogel_at_collab.net>
Date: 2005-05-05 01:18:43 CEST

kfogel@collab.net writes:
> But when we return a file in response to a generic DAV request, we
> have no idea what the user is going to do with it. In fact, it seems
> likely that someone using a generic DAV client to fetch a file will
> often not be obtaining a "text/plain" document. It's just as likely
> to be MSWord, Excel, whatever, and that some software consumers of the
> file would Do The Wrong Thing if they thought were plain text.

I wrote something slightly wrong here, but it doesn't change my point.

The 'else' clause in question activates when:

   a) There is no svn:mime-type already set
       - AND -
   b) Either the client is an svn client, OR it's not an svn client
      but Apache has no other mime-type it wants to use.

So we might be serving to a generic DAV client or not; we don't know.

But my main point is that Subversion doesn't actually assume something
is mime-type "text/plain" when it has no other information. Notice,
for example, that Subversion doesn't set a file's svn:mime-type
property to "text/plain" automatically (unless some conf file said to).

All Subversion does is treat the file as "text/plain" in a certain
well-understood circumstances. That's very different from slapping on
a mime-type that the whole world can see.

Hope I've been clearer this time,

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 5 01:51:54 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.