>>>>> On Wed, 7 Sep 2016 16:46:12 +0100, Mark Thomas <markt_at_apache.org> said:
EB> Do we specifically need to account for the case of collision between a
EB> header set by the app and one that is set by the container? If so, we
EB> must decide who wins, the container or the app. I judge the app should
EB> win. If so, the text could be rewritten as:
EB> Containers retain the right to add or modify headers before the
EB> response is committed. If a header is explicitly set by the
EB> application, containers must not change the header set in this way.
EB> I don't see the need for a statement about what sorts of headers the
EB> container generally needs to add.
EB> Thoughts?
MT> -1. The container should win. It will only be setting protocol required
MT> headers and those are something the application should not be
MT> interfering with.
If we choose "container wins" I propose the following then,
Containers retain the right to add or modify headers before the response
is committed. Any changes to such headers made by the application must
be ignored by the container.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017