[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 25 Aug 2009 11:41:41 +0300 (Jerusalem Daylight Time)

Would browsers behave differently if we sent *no* content-type header for
those files (instead of sending an explicit "application/octet-stream"

David Glasser wrote on Mon, 24 Aug 2009 at 18:04 -0700:
> On Mon, Aug 24, 2009 at 9:29 AM, C. Michael Pilato<cmpilato_at_collab.net> wrote:
> > Bert Huijben wrote:
> >>> If we can't figure out a good mime type to use, then we'll default to a
> >>> bag o' bytes: application/octet-stream.
> >>
> >> It seems this breaks browsing to text files via Firefox.
> >>
> > Yeah, I guess it would work fine if we set the svn:mime-type property on our
> > CHANGES file, though (to "text/plain").
> On the other hand, it's an irritating feature of many web browsers
> that there's no way to convince them to view an
> application/octet-stream file inline, whereas an erroneous text/plain
> should still support "save link as". I think using octet-stream as
> the default is likely to overall reduce usability of Subversion.
> --dave

Received on 2009-08-27 00:05:56 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.