At 1:44 AM -0400 6/16/06, Chris Shiflett wrote:
Richard Lynch wrote:
It is possible that all modern browsers have given
in to whichever johnny-come-lately 'standard' made
up the Content-disposition header.
The original RFC for it is dated June 1995, so it's not too recent. There are
plenty of
tedd schrieb:
At 1:44 AM -0400 6/16/06, Chris Shiflett wrote:
Richard Lynch wrote:
It is possible that all modern browsers have given
in to whichever johnny-come-lately 'standard' made
up the Content-disposition header.
The original RFC for it is dated June 1995, so it's not too recent. There
At 12:44 PM +0200 6/16/06, Barry wrote:
tedd schrieb:
At 1:44 AM -0400 6/16/06, Chris Shiflett wrote:
Richard Lynch wrote:
It is possible that all modern browsers have given
in to whichever johnny-come-lately 'standard' made
up the Content-disposition header.
The original RFC for it is dated June
tedd wrote:
Barry says you can use these three:
header(Content-Type: application/force-download);
header(Content-Type: application/octet-stream);
header(Content-Type: application/download);
Richard says only use this one:
header(Content-type: application/octet-stream);
And, you say use both.
-Original Message-
From: Chris Shiflett [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 9:11 AM
To: tedd
Cc: [EMAIL PROTECTED]; Barry; php-general@lists.php.net
Subject: Re: [PHP] Re: File Download Headers
tedd wrote:
Barry says you can use these three:
header(Content
I have now officially GIVEN UP on this thread.
On Fri, June 16, 2006 6:03 am, tedd wrote:
At 12:44 PM +0200 6/16/06, Barry wrote:
tedd schrieb:
At 1:44 AM -0400 6/16/06, Chris Shiflett wrote:
Richard Lynch wrote:
It is possible that all modern browsers have given
in to whichever
On Friday 16 June 2006 08:10, Chris Shiflett wrote:
Richard's example is the correct Content-Type to use. Barry's is no
different than this:
header('Content-Type: foo/bar');
It's better to use a valid type and to not have superfluous header()
calls that do nothing.
Hope that helps.
Barry wrote:
Richard Lynch schrieb:
and are all you can find from Google?
O_o
Anybody?
What?!?
Barry, chances are Richard was already initiating downloads
when you were still eating from a bottle.
I for myself use this:
header(Content-Type: application/force-download);
Jochem Maas schrieb:
Barry wrote:
Barry, chances are Richard was already initiating downloads
when you were still eating from a bottle.
I don't think so well because the Zuse had no network capability.
I for myself use this:
header(Content-Type: application/force-download);
Barry wrote:
You can send every header twice, triple. a zillion
times if you want.
Sure, but you have to know how to use header():
http://php.net/header
By default it will replace, but if you pass in FALSE as the second
argument you can force multiple headers of the same type.
Regardless,
Chris Shiflett schrieb:
Barry wrote:
You can send every header twice, triple. a zillion
times if you want.
Sure, but you have to know how to use header():
http://php.net/header
By default it will replace, but if you pass in FALSE as the second
argument you can force multiple headers of the
On Thu, June 15, 2006 3:04 am, Barry wrote:
Richard Lynch schrieb:
and are all you can find from Google?
O_o
Anybody?
What?!?
I for myself use this:
header(Content-Type: application/force-download);
header(Content-Type: application/octet-stream);
header(Content-Type:
On Thu, June 15, 2006 7:41 am, Chris Shiflett wrote:
Regardless, I think Content-Disposition is the header you need, not
Content-Type.
It is possible that all modern browsers have given in to whichever
johnny-come-lately 'standard' made up the Content-disposition header.
I know for sure it did
Richard Lynch wrote:
It is possible that all modern browsers have given
in to whichever johnny-come-lately 'standard' made
up the Content-disposition header.
The original RFC for it is dated June 1995, so it's not too recent.
There are plenty of useful aspects of HTTP not defined in RFC 2616.
14 matches
Mail list logo
