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

RE: svn commit: r36720 - trunk/subversion/mod_dav_svn

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Tue, 25 Aug 2009 13:58:46 +0200

On Mon, Aug 24, 2009 at 9:29 AM, C. Michael Pilato<cmpilato_at_collab.net> wrote:
> Yeah, I guess it would work fine if we set the svn:mime-type property on our
> CHANGES file, though (to "text/plain"). *shrug*. Extension-less files are
> always problematic for MIME type stuff. While most of the extension-less
> files in our tree may be human-readable, it's certainly conceivable that
> others would have extension-less files in their trees that aren't
> human-readable. It's a win-lose situation!

Note that not only extension-less files are affected currently. All the *.txt files under trunk/notes are also returned with "Content-Type: application/octet-stream", causing FF to popup its dialog to open or save the file.

Forgive my ignorance, but I don't really understand why this has changed. The old behavior was consistent with the way SVN considers files as text-files for diffing and merging. I.e. if a file has no mime-type svn will perform textual merges etc. (same as when it has a mime-type of text/*). Or am I wrong?

So I would consider it normal to fall back on text/plain as a Content-Type if there is no mime-type set. Or maybe, as Daniel suggested, send no Content-type (don't know if that would work for all browsers though)...

Kind regards,

Received on 2009-08-26 22:54:53 CEST

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.