Core API: the static resource filter should have access to the response object

[jri]

Currently the ResourceRequestFilterListener interface looks like:

void resourceRequestFilter(HttpServletRequest request)

The user should have access to the HttpServletResponse object as well, in order to e.g. add specific response headers:

void resourceRequestFilter(HttpServletRequest request, HttpServletResponse response)

This would be needed by the Files plugin in order to support downloading files through setting the Content-Disposition header (see #661).

[Jörg Richter <jri@…>]

In c378b17cbaf5617ee627c60b9fa1d3a33ed2eb5c/deepamehta:

Core API: extend static resource filter (#989).

BREAKING CHANGE

DM passes also the response object to the ResourceRequestFilterListener event handler:

void resourceRequestFilter(HttpServletRequest request, HttpServletResponse response)

This is useful to e.g. set specific response headers.

See #989.

[Jörg Richter <jri@…>]

In fb2ea54a3ec81e8b9875501d5c7f7d0f2f159fa2/deepamehta:

Core API: rename resourceRequestFilter() (#989).

BREAKING CHANGE

1 event listener interface renamed:

ResourceRequestFilterListener -> StaticResourceFilterListener

Corresponding handler method:

resourceRequestFilter() -> staticResourceFilter()

See #989.