It will be a backwards compatibility break, as minuscule as it is, and our
policy is to only do those (as practical) at major releases.  If it weren't
for that, I'm pretty sure nobody would miss the header if we deleted it now.

Just make the comment "Header will be removed at 4.0" and it'll be good.
 @deprecated tags are usually only used in class/method/var doc blocks.

On Saturday, June 22, 2013, Piotr wrote:

> In libraries/joomla/application/web.php:
>
> > @@ -390,7 +390,14 @@ protected function compress()
> >
> >  				// Set the encoding headers.
> >  				$this->setHeader('Content-Encoding', $encoding);
> > -				$this->setHeader('X-Content-Encoded-By', 'Joomla');
> > +
> > +				/*
> > +				 * Header to be removed in 14.1 (Platform) & 3.5 (CMS)
>
> That's for a reason. Why not 3.5?
>
>    - the issue is being reported since 1.5 days #22495<http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=22495>,
>
>    - there are no known backward compatibility issues
>
> Is it that deprecating is scheduled for 4.0?
>
> Should the comment look like that then?
>
> /* * @deprecated  4.0  Use JResponse::setHeader() instead */
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/joomla/joomla-cms/pull/1233/files#r4831566>
> .
>