[
https://issues.apache.org/jira/browse/WICKET-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059864#comment-13059864
]
Peter Ertl commented on WICKET-3845:
------------------------------------
Surprisingly(!) headers with empty values seem to be valid from looking at the
RFC:
url:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html
definition:
message-header = field-name ":" [ field-value ]
being compliant to the RFC is mandary *imho* so we should support this...
> support custom response headers in AbstractResource.ResourceResponse
> --------------------------------------------------------------------
>
> 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
> Assignee: Peter Ertl
> 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
