[Seaside] Dynamically serving contents for an iFrame
Philippe Marschall
philippe.marschall at gmail.com
Wed May 13 09:03:24 UTC 2015
On Tue, May 12, 2015 at 9:07 PM, jtuchel at objektfabrik.de
<jtuchel at objektfabrik.de> wrote:
> H iPhilippe,
>
> once again you nailed it.
>
> At first it didn't work when I did this:
>
>
> self requestContext respond: [:resp |
> resp
> inlineWithFileName: aWAFile fileName;
> document: aWAFile contents mimeType: aWAFile contentType
> fileName: aWAFile fileName;
> doNotCache]
>
> Then I tried:
>
> self requestContext respond: [:resp |
> resp
> inlineWithFileName: aWAFile fileName;
> document: aWAFile contents mimeType: aWAFile contentType;
> doNotCache]
>
>
> And it does work now.
>
>
> In the first situation the Content-Disposition header was always
> "attachment; filename=".
> I'm not sure if that is a bug or not. Just wanted to let you know.
This is a feature. "attachment" causes the download dialog to open,
"inline" just displays it. #fileName: triggers "attachement;
filename=".
> Again: Thank you very much!!!
>
> Maybe we can have some Vino in Brescia? At least one glass is on me!
:-)
Cheers
Philippe
More information about the seaside
mailing list