[
https://issues.apache.org/jira/browse/ISIS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013933#comment-16013933
]
Andi Huber edited comment on ISIS-1619 at 5/26/17 7:37 AM:
-----------------------------------------------------------
Fixed with PR #81
https://github.com/apache/isis/pull/81
was (Author: hobrom):
I've created a pull request to demonstrate a possible solution:
https://github.com/apache/isis/pull/79
> Blob/Clob Action results are cached no matter what
> --------------------------------------------------
>
> Key: ISIS-1619
> URL: https://issues.apache.org/jira/browse/ISIS-1619
> Project: Isis
> Issue Type: Bug
> Components: Core: Viewer: Wicket
> Affects Versions: 1.14.0
> Reporter: Andi Huber
> Fix For: 1.15.0
>
>
> If you click an Action that returns a Blob (download), the client receives a
> HTTP response header with an entry Pragma: "cache".
> If the Blob is dynamically changing with every request, the client will not
> see this changes. (As long as the request url stays the same.)
> Expected behavior would be (at least for this code snippet) to produce a new
> result with each invocation.
> {code:title=SimpleObjectMenu.java|borderStyle=solid}
> @Action(semantics=SemanticsOf.NON_IDEMPOTENT)
> public Blob download() {
> return new Blob("blob", "application/json",
> ("{\"now\" : \""+new java.util.Date()+"\"}").getBytes());
> }
> {code}
> But it does not!
> Steps to reproduce:
> Take the simple-app artifact 1.14 and add above snippet to the
> SimpleObjectMenu.
> Consecutive calls of the download action will not be updated. Instead the
> client/browser provides cached data from an earlier request.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
