Hi!
You are completely right, I forgot to put it in my commit message. The
"Compatibility" section of
https://httpd.apache.org/docs/trunk/mod/mod_headers.html#header is already
mentioning the >= 2.4.7 note so I thought to remove the duplicate.
If you feel that it would be better to restore it, I'll do it :)
Thanks!
Luca
2016-11-16 7:01 GMT+01:00 Marion & Christophe JAILLET <
christophe.jail...@wanadoo.fr>:
> Hi,
>
> why removing compatibility note (i.e. 2.4.7) ?
>
> CJ
>
>
>
> Le 15/11/2016 à 23:57, elu...@apache.org a écrit :
>
>> Author: elukey
>> Date: Tue Nov 15 22:57:36 2016
>> New Revision: 1769900
>>
>> URL: http://svn.apache.org/viewvc?rev=1769900=rev
>> Log:
>> documentation rebuild
>>
>> Modified:
>> httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en
>>
>> Modified: httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en
>> URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/m
>> od/mod_headers.html.en?rev=1769900=1769899=1769900=diff
>>
>> ==
>> --- httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en (original)
>> +++ httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en Tue Nov 15
>> 22:57:36 2016
>> @@ -309,8 +309,16 @@ available in 2.4.10 and later
>> setifempty
>> The request header is set, but only if there is no previous
>> header
>> -with this name.
>> -Available in 2.4.7 and later.
>> +with this name.
>> +
>> +The Content-Type header is a special use case since there might be
>> +the chance that its value have been determined but the header is not
>> part
>> +of the response when setifempty is evaluated.
>> +It is safer to use set for this use case like in the
>> +following example:
>> +Header set Content-Type
>> "text/plain" "expr=-z %{CONTENT_TYPE}"
>> +
>> +
>> unset
>> The response header of this name is removed, if it exists.
>>
>>
>>
>>
>
