Hi Manuel!
2016-05-27 14:28 GMT+02:00 Vacelet, Manuel <manuel.vace...@enalean.com>:
> Hi all,
>
> I got a weird behavior with apache 2.4.12 (from RHEL scl for that matter).
>
> I have a php application (behind fcgi/fpm) that sets Last-Modified header
> like:
> <?php header('Last-Modified: never');
>
> but when I curl the page, the header sent is:
> < Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT
>
> When the date is correct in my php app, the returned value is OK but as
> soon as it's not RFC valid, it's modified.
>
I am probably missing some bits of information, but what is the use case to
send a HTTP response with a well known header not following the RFC? I
didn't check the code but I would expect httpd to enforce the RFC when
needed rather than simply returning what the backend issues.
Thanks!
Luca
>
