From: Juerd Date: 20:27 on 30 May 2004 Subject: open in browser Yes, I know that it isn't text/plain. Yes, I know that you don't know how to handle that mime type. But please, PLEASE, can you just TRY to display it without forcing me to save it to disk or to use it with an external application (which also means saving it to disk)? Every browser should have a "open in browser" option in the download dialog that lets you just see the thing as if it's text/plain. I know I'm not the only one who wants this and I'm sure the feature has already been requested a thousand times. Why won't browser coders create this feature? Juerd
From: Thomas R. Sibley Date: 02:20 on 31 May 2004 Subject: Re: open in browser Juerd wrote on 05/30/04 15:27: > Every browser should have a "open in browser" option in the download > dialog that lets you just see the thing as if it's text/plain. I agree with you, BUT if admins fixed their servers to report the correct MIME types for cases where they don't (what kind of web server sends what is really text/plain as application/octet-stream!?), my use of such a feature would drop drastically. Tom
From: Juerd Date: 02:47 on 31 May 2004 Subject: Re: open in browser Thomas R. Sibley skribis 2004-05-30 21:20 (-0400): > Juerd wrote on 05/30/04 15:27: > >Every browser should have a "open in browser" option in the download > >dialog that lets you just see the thing as if it's text/plain. > I agree with you, BUT if admins fixed their servers to report the > correct MIME types for cases where they don't (what kind of web server > sends what is really text/plain as application/octet-stream!?), my use > of such a feature would drop drastically. I actually want it because the MIME type is communicated correctly. Long time ago, almost anything that wasn't text/html or an image would get sent as text/plain. And life was sort-of good, with annoying screenfuls of garbage now and then. But now, perl scripts are perl scripts and real media thingies with just an url in it are real media thingies with just an url in it. Sometimes (most of the time), I want to just view the text without too much hassle. Juerd
From: Thomas R. Sibley Date: 03:01 on 31 May 2004 Subject: Re: open in browser Juerd wrote on 05/30/04 21:47: > But now, perl scripts are perl scripts and real media thingies with just > an url in it are real media thingies with just an url in it. Sometimes > (most of the time), I want to just view the text without too much > hassle. Yeah, that real media thing is one use I'd have for such a feature. My current solution is (in one of the many xterms open): GET http://foo.bar/some/url.rm and then copy & paste to run: realone [URL] But it would be nicer from within the browser... (for cases where the mplayer or real plugins don't work or I don't want to use them) Tom
From: Juerd Date: 03:22 on 31 May 2004 Subject: Re: open in browser Thomas R. Sibley skribis 2004-05-30 22:01 (-0400): > GET http://foo.bar/some/url.rm Referr?er checks. :( Juerd
From: Geoff Richards Date: 16:59 on 31 May 2004 Subject: Re: open in browser On Mon, May 31, 2004 at 04:22:54AM +0200, Juerd wrote: > Thomas R. Sibley skribis 2004-05-30 22:01 (-0400): > > GET http://foo.bar/some/url.rm > > Referr?er checks. :( wget --referer=blah http://foo.bar/some/url.rm
From: Thomas R. Sibley Date: 18:27 on 31 May 2004 Subject: Re: open in browser Geoff Richards wrote on 05/31/04 11:59: >>Referr?er checks. :( > > wget --referer=blah http://foo.bar/some/url.rm Actually, I've never had a problem with referrer checks when dealing with real media specifically. But yes, wget is nice for that. T.
From: Philip Newton Date: 11:41 on 01 Jun 2004 Subject: Re: open in browser On 31 May 2004 at 16:59, Geoff Richards wrote: > On Mon, May 31, 2004 at 04:22:54AM +0200, Juerd wrote: > > Thomas R. Sibley skribis 2004-05-30 22:01 (-0400): > > > GET http://foo.bar/some/url.rm > > > > Referr?er checks. :( > > wget --referer=blah http://foo.bar/some/url.rm Or GET -H 'Referer: blah' http://foo.bar/some/url.rm . Cheers, Philip
From: Abigail Date: 22:47 on 31 May 2004 Subject: Re: open in browser On Sun, May 30, 2004 at 09:27:21PM +0200, Juerd wrote: > Yes, I know that it isn't text/plain. > > Yes, I know that you don't know how to handle that mime type. > > But please, PLEASE, can you just TRY to display it without forcing me to > save it to disk or to use it with an external application (which also > means saving it to disk)? Yeah, and also, if it's a compressed tarfile, could you please, please save it to disk, instead of uncompressing it and displaying me the tar file in the browser? Abigail
From: Juerd Date: 23:10 on 31 May 2004 Subject: Re: open in browser Abigail skribis 2004-05-31 23:47 (+0200): > Yeah, and also, if it's a compressed tarfile, could you please, please > save it to disk, instead of uncompressing it and displaying me the tar > file in the browser? Last time I had that was when I still used Netscape 4 :) Although *that* would also happily show me the content of non-text/plain as text/plain. Juerd
From: peter (Peter da Silva) Date: 00:13 on 01 Jun 2004 Subject: Re: open in browser > Yeah, and also, if it's a compressed tarfile, could you please, please > save it to disk, instead of uncompressing it and displaying me the tar > file in the browser? Oh, yes, and all the variants thereof. If it's compressed text/html, OK, you can uncompress it. That's a useful efficiency hack. ANYTHING ELSE, YOU DIRTY BEGGAR, IS BINARY While I'm about it, HEY, APPLE, when I set my default in textEdit to plain text, that means I want you to open text.html as plain text, NOT pass it off to the magic RTF fairy for clobberization.
Generated at 10:27 on 16 Apr 2008 by mariachi