[
https://issues.apache.org/jira/browse/WICKET-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057891#comment-13057891
]
Peter Ertl commented on WICKET-3845:
------------------------------------
I think you should be able to set the headers inside #newResourceResponse()
when actually creating the response to have all the context information
available for setting headers that relate to that content. For example you
could conditionally downscale an image resource and set header
"X-Original-Size" with the original image dimensions. Doing things like that
with an callback will be very hard.
> There is not a good way to use custom response headers with AbstractResource
> ----------------------------------------------------------------------------
>
> Key: WICKET-3845
> URL: https://issues.apache.org/jira/browse/WICKET-3845
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC5.1
> Reporter: Adriano dos Santos Fernandes
> Fix For: 1.5-RC6
>
> Attachments: custom-headers.patch, wicket-3845.patch
>
>
> I'm converting an application to Wicket 1.5 and I see some problems with
> resources.
> There is a case I need to add headers (not present in ResourceResponse
> properties) and it looks ugly.
> This is what I need to do:
> @Override
> protected void configureCache(ResourceResponse data, Attributes
> attributes)
> {
> super.configureCache(data, attributes);
> ((WebResponse) attributes.getResponse()).setHeader("Accept-Ranges",
> "bytes");
> }
> It's a hack to use configureCache here, but this can't be added to
> setResponseHeaders, which seams a better apparent method name for it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
