  string, and discard the iterator.
  
  .. versionchanged:: 1.5
  
  You can now use :class:`HttpResponse` as a file-like object even if it was
  instantiated with an iterator. Django will consume and save the content of
  the iterator on first access.
  
  Setting headers
  ~~~~~~~~~~~~~~~
  
  To set or remove a header in your response, treat it like a dictionary::
 
</s> remove As of Django 1.7, when :class:`HttpResponse` is instantiated with an
iterator, it will consume it immediately, store the response content as a
string, and discard the iterator.
 </s> add     As of Django 1.7, when :class:`HttpResponse` is instantiated with an
    iterator, it will consume it immediately, store the response content as a
    string, and discard the iterator. </s> remove This technique is fragile and was deprecated in Django 1.5. If you need the
response to be streamed from the iterator to the client, you should use the
:class:`StreamingHttpResponse` class instead.
 </s> add     This technique is fragile and was deprecated in Django 1.5. If you need the
    response to be streamed from the iterator to the client, you should use the
    :class:`StreamingHttpResponse` class instead. </s> remove .. versionchanged:: 1.5

 </s> add  </s> remove Django used to remove the ``cleaned_data`` attribute entirely if there were
any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
the form doesn't validate, but it contains only field values that did
validate.
 </s> add     Django used to remove the ``cleaned_data`` attribute entirely if there were
    any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
    the form doesn't validate, but it contains only field values that did
    validate. </s> remove .. versionchanged:: 1.5

 </s> add 
    You can now use :class:`HttpResponse` as a file-like object even if it was
    instantiated with an iterator. Django will consume and save the content of
    the iterator on first access.
  string, and discard the iterator.
  
  .. versionchanged:: 1.5
  
    You can now use :class:`HttpResponse` as a file-like object even if it was
    instantiated with an iterator. Django will consume and save the content of
    the iterator on first access.
    You can now use :class:`HttpResponse` as a file-like object even if it was
    instantiated with an iterator. Django will consume and save the content of
    the iterator on first access.
    You can now use :class:`HttpResponse` as a file-like object even if it was
    instantiated with an iterator. Django will consume and save the content of
    the iterator on first access.
  
  Setting headers
  ~~~~~~~~~~~~~~~
  
  To set or remove a header in your response, treat it like a dictionary::
keep keep keep keep replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/ref/request-response.txt