header

(PHP 4, PHP 5, PHP 7, PHP 8)

header — Envia um cabeçalho HTTP bruto

Descrição

header(string $header, bool $replace = true, int $response_code = 0): void

header() é usada para enviar um cabeçalho HTTP bruto. Consulte a » especificação HTTP/1.1 para obter mais informações sobre cabeçalhos HTTP.

Lembre-se de que header() deve ser chamada antes de qualquer saída real ser enviada, seja por tags HTML normais, linhas em branco em um arquivo ou pelo PHP. É um erro muito comum ler código com include, require, funções ou outra função de acesso a arquivo, e ter espaços ou linhas vazias que são exibidas antes de header() ser chamada. O mesmo problema existe ao usar um único arquivo PHP/HTML.

<html>
<?php
/* Isso causará um erro. Observe a saída
 * acima, que é antes da chamada header() */
header('Location: http://www.example.com/');
exit;
?>

Parâmetros

header

A string do cabeçalho.

Existem dois casos especiais de chamadas de cabeçalho. O primeiro é um cabeçalho que começa com a string "HTTP/" (maiúsculas ou minúsculas, não importa), que será usado para descobrir o código de status HTTP a ser enviado. Por exemplo, se o Apache foi configurado para usar um script PHP para lidar com solicitações de arquivos ausentes (usando a diretiva ErrorDocument), é importante ter certeza de que o script gera o código de status adequado.

<?php
// Este exemplo ilustra o caso especial "HTTP/"
// Alternativas melhores em casos de uso típico incluem:
// 1. header($_SERVER["SERVER_PROTOCOL"] . " 404 Not Found");
//    (para substituir as mensagens de status HTTP para clientes que ainda estão usando HTTP/1.0)
// 2. http_response_code(404); (para usar a mensagem padrão)
header("HTTP/1.1 404 Not Found");
?>

O segunda caso especial é o cabeçalho "Location:". Ele não só envia o cabeçalho de volta para o navegador, mas também retorna um código de status REDIRECT (302) para o navegador a menos que o código de status 201 ou um 3xx já tenha sido enviado.

<?php
header("Location: http://www.example.com/"); /* Redireciona o navegador */

/* Certificando que o restante do código não seja executado quando o redirecionamento é feito. */
exit;
?>

replace

O parâmetro opcional replace indica se o cabeçalho deve substituir um cabeçalho semelhante anterior ou adicionar um segundo cabeçalho do mesmo tipo. Por padrão ele irá substituir, mas se for passado false como segundo argumento podem ser forçados vários cabeçalhos do mesmo tipo. Por exemplo:

<?php
header('WWW-Authenticate: Negotiate');
header('WWW-Authenticate: NTLM', false);
?>

response_code

Força o código de resposta HTTP para o valor especificado. Observe que este parâmetro só tem efeito se o parâmetro header não estiver vazio.

Valor Retornado

Nenhum valor é retornado.

Erros/Exceções

Em caso de falha ao programar o envio do cabeçalho, header() emitirá um erro de nível E_WARNING.

Exemplos

Exemplo #1 Caixa de diálogo para salvar arquivo

Se quiser que o usuário seja solicitado a salvar os dados que estão sendo enviados, como um arquivo PDF gerado por exemplo, pode ser usado o cabeçalho » Content-Disposition para fornecer um nome de arquivo recomendado e forçar o navegador a exibir a caixa de diálogo para salvá-lo.

<?php
// A saída será um PDF
header('Content-Type: application/pdf');

// Será chamado de downloaded.pdf
header('Content-Disposition: attachment; filename="downloaded.pdf"');

// A fonte do PDF está em original.pdf
readfile('original.pdf');
?>

Exemplo #2 Diretivas de cache

Os scripts PHP geralmente geram conteúdo dinâmico que não deve ser armazenado em cache pelo navegador do cliente ou por qualquer cache proxy entre o servidor e o navegador do cliente. Muitos proxies e clientes podem ser forçados a desabilitar o cache com:

<?php
header("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
header("Expires: Sat, 03 Dec 2016 17:15:00 GMT"); // Data no passado
?>

Nota:
Pode acontecer das páginas não serem armazenadas em cache mesmo que todos os cabeçalhos acima não sejam gerados. Há uma série de opções que os usuários podem definir para seus navegadores que alteram seu comportamento padrão de cache. Ao enviar os cabeçalhos acima, devem ser substituídas quaisquer configurações que possam fazer com que a saída do script seja armazenada em cache.

Além disso, session_cache_limiter() e a configuração session.cache_limiter podem ser usadas para gerar automaticamente os cabeçalhos corretos relacionados ao cache quando sessões estão sendo usadas.

Exemplo #3 Definindo um cookie

setcookie() fornece uma maneira conveniente de definir cookies. Para definir um cookie que inclui atributos que setcookie() não suporta, header() can be used.

Por exemplo, o código a seguir define um cookie que inclui um atributo Partitioned.

<?php
header('Set-Cookie: name=value; Secure; Path=/; SameSite=None; Partitioned;');
?>

Notas

Nota:
Os cabeçalhos só serão acessíveis e enviados quando uma SAPI que os suporta estiver em uso.

Nota:
Para contornar esse problema, o buffer de saída pode ser usado, com a sobrecarga de toda a saída para o navegador sendo armazenada em buffer no servidor até seja enviada. Isso pode ser feito chamando ob_start() e ob_end_flush() no script, ou definindo a diretiva de configuração output_buffering no arquivo php.ini ou nos arquivos de configuração do servidor.

Nota:
A linha do cabeçalho de status HTTP sempre será a primeira enviada ao cliente, independentemente de a chamada a header() ser a primeira ou não. O status pode ser substituído chamando header() com uma nova linha de status a qualquer momento, a menos que os cabeçalhos HTTP já tenham sido enviados.

Nota:
A maioria dos clientes atuais aceita URI relativo como argumento para » Local:, mas alguns clientes mais antigos exigem um URI absoluto incluindo o esquema, nome do host e caminho absoluto. Geralmente, podem ser usados $_SERVER['HTTP_HOST'], $_SERVER['PHP_SELF'] e dirname() para criar um URI absoluto a partir de um relativo:

<?php /* Redireciona para uma página diferente no diretório atual que foi solicitado */ $host = $_SERVER['HTTP_HOST']; $uri = rtrim(dirname($_SERVER['PHP_SELF']), '/\\'); $extra = 'minha_pagina.php'; header("Location: http://$host$uri/$extra"); exit; ?>

Nota:
O ID da sessão não é passado com o cabeçalho "Location:" mesmo se session.use_trans_sid estiver ativada. Deve ser passado manualmente usando a constante SID.

Veja Também

headers_sent() - Verifica se ou onde os cabeçalhos foram enviados
setcookie() - Envia um cookie
http_response_code() - Obtém ou define o código de resposta HTTP
header_remove() - Remove cabeçalhos definidos anteriormente
headers_list() - Retorna uma lista de cabeçalhos de resposta enviados (ou prontos para enviar)
A seção sobre autenticação HTTP

Melhore Esta Página

Aprenda Como Melhorar Esta Página • Envie uma Solicitação de Modificação • Reporte um Problema

＋adicione uma nota

Notas Enviadas por Usuários (em inglês) 26 notes

down

247

mjt at jpeto dot net ¶

15 years ago

I strongly recommend, that you use



header($_SERVER["SERVER_PROTOCOL"]." 404 Not Found");



instead of 



header("HTTP/1.1 404 Not Found");



I had big troubles with an Apache/2.0.59 (Unix) answering in HTTP/1.0 while I (accidentially) added a "HTTP/1.1 200 Ok" - Header.



Most of the pages were displayed correct, but on some of them apache added weird content to it:



A 4-digits HexCode on top of the page (before any output of my php script), seems to be some kind of checksum, because it changes from page to page and browser to browser. (same code for same page and browser)



"0" at the bottom of the page (after the complete output of my php script) 



It took me quite a while to find out about the wrong protocol in the HTTP-header.

down

169

Marcel G ¶

14 years ago

Several times this one is asked on the net but an answer could not be found in the docs on php.net ...



If you want to redirect an user and tell him he will be redirected, e. g. "You will be redirected in about 5 secs. If not, click here." you cannot use header( 'Location: ...' ) as you can't sent any output before the headers are sent.



So, either you have to use the HTML meta refresh thingy or you use the following:



<?php

  header( "refresh:5;url=wherever.php" );

  echo 'You\'ll be redirected in about 5 secs. If not, click <a href="wherever.php">here</a>.';

?>



Hth someone

down

Dylan at WeDefy dot com ¶

17 years ago

A quick way to make redirects permanent or temporary is to make use of the $http_response_code parameter in header().

<?php
// 301 Moved Permanently
header("Location: /foo.php",TRUE,301);

// 302 Found
header("Location: /foo.php",TRUE,302);
header("Location: /foo.php");

// 303 See Other
header("Location: /foo.php",TRUE,303);

// 307 Temporary Redirect
header("Location: /foo.php",TRUE,307);
?>

The HTTP status code changes the way browsers and robots handle redirects, so if you are using header(Location:) it's a good idea to set the status code at the same time.  Browsers typically re-request a 307 page every time, cache a 302 page for the session, and cache a 301 page for longer, or even indefinitely.  Search engines typically transfer "page rank" to the new location for 301 redirects, but not for 302, 303 or 307. If the status code is not specified, header('Location:') defaults to 302.

down

mandor at mandor dot net ¶

18 years ago

When using PHP to output an image, it won't be cached by the client so if you don't want them to download the image each time they reload the page, you will need to emulate part of the HTTP protocol.

Here's how:

<?php

    // Test image.
    $fn = '/test/foo.png';

    // Getting headers sent by the client.
    $headers = apache_request_headers(); 

    // Checking if the client is validating his cache and if it is current.
    if (isset($headers['If-Modified-Since']) && (strtotime($headers['If-Modified-Since']) == filemtime($fn))) {
        // Client's cache IS current, so we just respond '304 Not Modified'.
        header('Last-Modified: '.gmdate('D, d M Y H:i:s', filemtime($fn)).' GMT', true, 304);
    } else {
        // Image not cached or cache outdated, we respond '200 OK' and output the image.
        header('Last-Modified: '.gmdate('D, d M Y H:i:s', filemtime($fn)).' GMT', true, 200);
        header('Content-Length: '.filesize($fn));
        header('Content-Type: image/png');
        print file_get_contents($fn);
    }

?>

That way foo.png will be properly cached by the client and you'll save bandwith. :)

down

Emmanuel Chazard ¶

1 year ago

If you use header() to allow the user to download a file, it's very important to check the encoding of the script itself. Your script should be encoded in UTF-8, but definitely not in UTF-8-BOM! The presence of BOM will alter the file received by the user. Let the following script: 

<?php 

$content = file_get_contents('test_download.png') ;
$name = 'test.png' ;
$size = strlen($content) ;
    
header('Content-Description: File Transfer');
header('Content-Type: application/octet-stream');
header('Cache-Control: no-cache, must-revalidate');
header('Expires: 0');
header('Content-Disposition: attachment; filename="'.$name.'"');
header('Content-Length: ' . $size);
header('Pragma: public');

echo $content ;

?>

Irrespectively from the encoding of test_download.png, when this PHP script is encoded in UTF-8-BOM, the content received by the user is different: 
- a ZWNBSP byte (U+FEFF) is added to the beginning of the file
- the file content is truncated!!!
If it's a binary file (e.g. image, proprietary format), the file will become unreadable.

down

php at ober-mail dot de ¶

4 years ago

Since PHP 5.4, the function `http_response_code()` can be used to set the response code instead of using the `header()` function, which requires to also set the correct protocol version (which can lead to problems, as seen in other comments).

down

bebertjean at yahoo dot fr ¶

15 years ago

If using the 'header' function for the downloading of files, especially if you're passing the filename as a variable, remember to surround the filename with double quotes, otherwise you'll have problems in Firefox as soon as there's a space in the filename.

So instead of typing:

<?php
  header("Content-Disposition: attachment; filename=" . basename($filename));
?>

you should type:

<?php
  header("Content-Disposition: attachment; filename=\"" . basename($filename) . "\"");
?>

If you don't do this then when the user clicks on the link for a file named "Example file with spaces.txt", then Firefox's Save As dialog box will give it the name "Example", and it will have no extension.

See the page called "Filenames_with_spaces_are_truncated_upon_download" at 
http://kb.mozillazine.org/ for more information. (Sorry, the site won't let me post such a long link...)

down

David Spector ¶

3 years ago

Please note that there is no error checking for the header command, either in PHP, browsers, or Web Developer Tools.

If you use something like "header('text/javascript');" to set the MIME type for PHP response text (such as for echoed or Included data), you will get an undiagnosed failure.

The proper MIME-setting function is "header('Content-type: text/javascript');".

down

yjf_victor ¶

8 years ago

According to the RFC 6226 (https://tools.ietf.org/html/rfc6266), the only way to send Content-Disposition Header with encoding is:

Content-Disposition: attachment;
                          filename*= UTF-8''%e2%82%ac%20rates

for backward compatibility, what should be sent is:

Content-Disposition: attachment;
                          filename="EURO rates";
                          filename*=utf-8''%e2%82%ac%20rates

As a result, we should use

<?php
$filename = '中文文件名.exe';   // a filename in Chinese characters

$contentDispositionField = 'Content-Disposition: attachment; '
    . sprintf('filename="%s"; ', rawurlencode($filename))
    . sprintf("filename*=utf-8''%s", rawurlencode($filename));

header('Content-Type: application/octet-stream');

header($contentDispositionField);

readfile('file_to_download.exe');
?>

I have tested the code in IE6-10, firefox and Chrome.

down

sk89q ¶

16 years ago

You can use HTTP's etags and last modified dates to ensure that you're not sending the browser data it already has cached.



<?php

$last_modified_time = filemtime($file);

$etag = md5_file($file);



header("Last-Modified: ".gmdate("D, d M Y H:i:s", $last_modified_time)." GMT");

header("Etag: $etag");



if (@strtotime($_SERVER['HTTP_IF_MODIFIED_SINCE']) == $last_modified_time ||

    trim($_SERVER['HTTP_IF_NONE_MATCH']) == $etag) {

    header("HTTP/1.1 304 Not Modified");

    exit;

}

?>

down

nospam at nospam dot com ¶

8 years ago

<?php

// Response codes behaviors when using 
header('Location: /target.php', true, $code) to forward user to another page:

$code = 301;
// Use when the old page has been "permanently moved and any future requests should be sent to the target page instead. PageRank may be transferred."

$code = 302; (default)
// "Temporary redirect so page is only cached if indicated by a Cache-Control or Expires header field."

$code = 303;
// "This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource and is not cached."

$code = 307;
// Beware that when used after a form is submitted using POST, it would carry over the posted values to the next page, such if target.php contains a form processing script, it will process the submitted info again!

// In other words, use 301 if permanent, 302 if temporary, and 303 if a results page from a submitted form.
// Maybe use 307 if a form processing script has moved.

?>

down

tim at sharpwebdevelopment dot com ¶

6 years ago

The header call can be misleading to novice php users.
when "header call" is stated, it refers the the top leftmost position of the file and not the "header()" function itself.
"<?php" opening tag must be placed before anything else, even whitespace.

down

David ¶

7 years ago

It seems the note saying the URI must be absolute is obsolete. Found on https://en.wikipedia.org/wiki/HTTP_location

«An obsolete version of the HTTP 1.1 specifications (IETF RFC 2616) required a complete absolute URI for redirection.[2] The IETF HTTP working group found that the most popular web browsers tolerate the passing of a relative URL[3] and, consequently, the updated HTTP 1.1 specifications (IETF RFC 7231) relaxed the original constraint, allowing the use of relative URLs in Location headers.»

down

ben at indietorrent dot org ¶

12 years ago

Be aware that sending binary files to the user-agent (browser) over an encrypted connection (SSL/TLS) will fail in IE (Internet Explorer) versions 5, 6, 7, and 8 if any of the following headers is included:

Cache-control:no-store
Cache-control:no-cache

See: http://support.microsoft.com/kb/323308

Workaround: do not send those headers.

Also, be aware that IE versions 5, 6, 7, and 8 double-compress already-compressed files and do not reverse the process correctly, so ZIP files and similar are corrupted on download.

Workaround: disable compression (beyond text/html) for these particular versions of IE, e.g., using Apache's "BrowserMatch" directive. The following example disables compression in all versions of IE:

BrowserMatch ".*MSIE.*" gzip-only-text/html

down

chris at ocproducts dot com ¶

7 years ago

Note that 'session_start' may overwrite your custom cache headers.
To remedy this you need to call:

session_cache_limiter('');

...after you set your custom cache headers. It will tell the PHP session code to not do any cache header changes of its own.

down

jp at webgraphe dot com ¶

20 years ago

A call to session_write_close() before the statement



<?php

    header("Location: URL");

    exit();

?>



is recommended if you want to be sure the session is updated before proceeding to the redirection.



We encountered a situation where the script accessed by the redirection wasn't loading the session correctly because the precedent script hadn't the time to update it (we used a database handler).



JP.

down

shutout2730 at yahoo dot com ¶

16 years ago

It is important to note that headers are actually sent when the first byte is output to the browser. If you are replacing headers in your scripts, this means that the placement of echo/print statements and output buffers may actually impact which headers are sent. In the case of redirects, if you forget to terminate your script after sending the header, adding a buffer or sending a character may change which page your users are sent to.

This redirects to 2.html since the second header replaces the first.

<?php
header("location: 1.html"); 
header("location: 2.html"); //replaces 1.html
?>

This redirects to 1.html since the header is sent as soon as the echo happens. You also won't see any "headers already sent" errors because the browser follows the redirect before it can display the error.

<?php
header("location: 1.html");
echo "send data"; 
header("location: 2.html"); //1.html already sent 
?>

Wrapping the previous example in an output buffer actually changes the behavior of the script! This is because headers aren't sent until the output buffer is flushed.

<?php
ob_start();
header("location: 1.html"); 
echo "send data"; 
header("location: 2.html"); //replaces 1.html
ob_end_flush(); //now the headers are sent
?>

down

Refugnic ¶

14 years ago

My files are in a compressed state (bz2). When the user clicks the link, I want them to get the uncompressed version of the file.

After decompressing the file, I ran into the problem, that the download dialog would always pop up, even when I told the dialog to 'Always perform this operation with this file type'.

As I found out, the problem was in the header directive 'Content-Disposition', namely the 'attachment' directive.

If you want your browser to simulate a plain link to a file, either change 'attachment' to 'inline' or omit it alltogether and you'll be fine.

This took me a while to figure out and I hope it will help someone else out there, who runs into the same problem.

down

dev at omikrosys dot com ¶

15 years ago

Just to inform you all, do not get confused between Content-Transfer-Encoding and Content-Encoding

Content-Transfer-Encoding specifies the encoding used to transfer the data within the HTTP protocol, like raw binary or base64. (binary is more compact than base64. base64 having 33% overhead).
Eg Use:- header('Content-Transfer-Encoding: binary');

Content-Encoding is used to apply things like gzip compression to the content/data.
Eg Use:- header('Content-Encoding: gzip');

down

-1

razvan_bc at yahoo dot com ¶

6 years ago

<?php
/* This will give an error. Note the output
 * above, which is before the header() call */
header('Location: http://www.example.com/');
exit;
?>

this example is pretty good BUT in time you use "exit" the parser will still work to decide what's happening next the "exit" 's action should do ('cause if you check the manual exit works in others situations too).
SO MY POINT IS : you should use :
<?php

header('Location: http://www.example.com/');
die();

?>
'CAUSE all die function does is to stop the script ,there is no other place for interpretation and the scope you choose to break the action of your script is quickly DONE!!!

there are many situations  with others examples and the right choose for small parts of your scrips that make differences when you write your php framework at well! 

Thanks Rasmus Lerdorf and his team to wrap off parts of unusual php functionality ,php 7 roolez!!!!!

down

scott at lucentminds dot com ¶

15 years ago

If you want to remove a header and keep it from being sent as part of the header response, just provide nothing as the header value after the header name. For example...

PHP, by default, always returns the following header:

"Content-Type: text/html"

Which your entire header response will look like

HTTP/1.1 200 OK
Server: Apache/2.2.11 (Unix)
X-Powered-By: PHP/5.2.8
Date: Fri, 16 Oct 2009 23:05:07 GMT
Content-Type: text/html; charset=UTF-8
Connection: close

If you call the header name with no value like so...

<?php

    header( 'Content-Type:' );

?>

Your headers now look like this:

HTTP/1.1 200 OK
Server: Apache/2.2.11 (Unix)
X-Powered-By: PHP/5.2.8
Date: Fri, 16 Oct 2009 23:05:07 GMT
Connection: close

down

Anonymous ¶

15 years ago

I just want to add, becuase I see here lots of wrong formated headers.



1. All used headers have first letters uppercase, so you MUST follow this. For example:



Location, not location

Content-Type, not content-type, nor CONTENT-TYPE



2. Then there MUST be colon and space, like



good: header("Content-Type: text/plain");

wrong: header("Content-Type:text/plain");



3. Location header MUST be absolute uri with scheme, domain, port, path, etc.



good: header("Location: http://www.example.com/something.php?a=1");



4. Relative URIs are NOT allowed



wrong:  Location: /something.php?a=1

wrong:  Location: ?a=1



It will make proxy server and http clients happier.

down

mzheng[no-spam-thx] at ariba dot com ¶

16 years ago

For large files (100+ MBs), I found that it is essential to flush the file content ASAP, otherwise the download dialog doesn't show until a long time or never. 

<?php
header("Content-Disposition: attachment; filename=" . urlencode($file));    
header("Content-Type: application/force-download");
header("Content-Type: application/octet-stream");
header("Content-Type: application/download");
header("Content-Description: File Transfer");             
header("Content-Length: " . filesize($file));
flush(); // this doesn't really matter.

$fp = fopen($file, "r"); 
while (!feof($fp))
{
    echo fread($fp, 65536); 
    flush(); // this is essential for large downloads
}  
fclose($fp); 
?>

down

-2

Vinay Kotekar ¶

9 years ago

Saving php file in ANSI  no isuess but when saving the file in UTF-8 format for various reasons remember to save the file without any BOM ( byte-order mark) support.
Otherwise you will face problem of headers not being properly sent 
eg. 
<?php header("Set-Cookie: name=user");?>

Would give something like this :-

Warning: Cannot modify header information - headers already sent by (output started at C:\www\info.php:1) in C:\www\info.php on line 1

down

-1

Cody G. ¶

14 years ago

After lots of research and testing, I'd like to share my findings about my problems with Internet Explorer and file downloads.

  Take a look at this code, which replicates the normal download of a Javascript:

<?php
 if(strstr($_SERVER["HTTP_USER_AGENT"],"MSIE")==false) {
  header("Content-type: text/javascript");
  header("Content-Disposition: inline; filename=\"download.js\"");
  header("Content-Length: ".filesize("my-file.js"));
 } else {
  header("Content-type: application/force-download");
  header("Content-Disposition: attachment; filename=\"download.js\"");
  header("Content-Length: ".filesize("my-file.js"));
 }
 header("Expires: Fri, 01 Jan 2010 05:00:00 GMT");
 if(strstr($_SERVER["HTTP_USER_AGENT"],"MSIE")==false) {
  header("Cache-Control: no-cache");
  header("Pragma: no-cache");
 }
 include("my-file.js");
?>

Now let me explain:

  I start out by checking for IE, then if not IE, I set Content-type (case-sensitive) to JS and set Content-Disposition (every header is case-sensitive from now on) to inline, because most browsers outside of IE like to display JS inline. (User may change settings). The Content-Length header is required by some browsers to activate download box. Then, if it is IE, the "application/force-download" Content-type is sometimes required to show the download box. Use this if you don't want your PDF to display in the browser (in IE). I use it here to make sure the box opens. Anyway, I set the Content-Disposition to attachment because I already know that the box will appear. Then I have the Content-Length again.

  Now, here's my big point. I have the Cache-Control and Pragma headers sent only if not IE. THESE HEADERS WILL PREVENT DOWNLOAD ON IE!!! Only use the Expires header, after all, it will require the file to be downloaded again the next time. This is not a bug! IE stores downloads in the Temporary Internet Files folder until the download is complete. I know this because once I downloaded a huge file to My Documents, but the Download Dialog box put it in the Temp folder and moved it at the end. Just think about it. If IE requires the file to be downloaded to the Temp folder, setting the Cache-Control and Pragma headers will cause an error!

I hope this saves someone some time!
~Cody G.

down

-3

Angelica Perduta ¶

4 years ago

I made a script that generates an optimized image for use on web pages using a 404 script to resize and reduce original images, but on some servers it was generating the image but then not using it due to some kind of cache somewhere of the 404 status. I managed to get it to work with the following and although I don't quite understand it, I hope my posting here does help others with similar issues:

    header_remove();
    header("Cache-Control: no-store, no-cache, must-revalidate, max-age=0");
    header("Cache-Control: post-check=0, pre-check=0", false);
    header("Pragma: no-cache");
    // ... and then try redirecting
    // 201 = The request has been fulfilled, resulting in the creation of a new resource however it's still not loading
    // 302 "moved temporarily" does seems to load it!
    header("location:$dst", FALSE, 302); // redirect to the file now we have it

＋adicione uma nota