Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Stefan Droog <sdroog@educator.eu>
To: "'users@jackrabbit.apache.org'" <users@jackrabbit.apache.org>
Date: Thu, 14 May 2009 16:10:57 +0200
Subject: RE: Creating PDF/PNG/TXT from inputstream doesn't work, JPG/html
 does
Thread-Topic: Creating PDF/PNG/TXT from inputstream doesn't work, JPG/html
 does
Thread-Index: AcnUm8GSb8edN/XATO+4P20F9jUdNgAAbnNA
Message-ID: <C55F36AD3838F44AA99978C58E96677E6CBF5D92@EX-NL-U1.vanenburg.com>
References: <C55F36AD3838F44AA99978C58E96677E6CBF5D91@EX-NL-U1.vanenburg.com>
 <4A0C22DC.4050609@gmx.de>
In-Reply-To: <4A0C22DC.4050609@gmx.de>
Accept-Language: nl-NL, en-US
Content-Language: en-US
acceptlanguage: nl-NL, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Currently it is all HTTP (localhost)

Header looks like
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Disposition: attachment; filename=3D"3000th.Release.pdf"
Content-Type: application/pdf
Date: Thu, 14 May 2009 14:05:05 GMT
Content-Length: 27214

Original file is 2,080 KB


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Thursday, May 14, 2009 3:56 PM
To: users@jackrabbit.apache.org
Subject: Re: Creating PDF/PNG/TXT from inputstream doesn't work, JPG/html d=
oes

Stefan Droog wrote:
> I want to send e.g. a PDF file to the client. It does work for JPG and Ht=
ml but not for PDF / PNG / TXT files.
> ...

I'd start by looking at an HTTP trace (the content is served over HTTP,
right?).

BR, Julian

The information contained in this communication is confidential, intended s=
olely for the use of the individual or entity to whom it is addressed and m=
ay be legally privileged and protected by professional secrecy. Access to t=
his message by anyone else is unauthorized. If you are not the intended rec=
ipient, any disclosure, copying, or distribution of the message, or any act=
ion or omission taken by you in reliance on it is prohibited and may be unl=
awful. Please immediately contact the sender if you have received this mess=
age in error. This email does not constitute any commitment from Cordys Hol=
ding BV or any of its subsidiaries except when expressly agreed in a writte=
n agreement between the intended recipient and Cordys Holding BV or its sub=
sidiaries. Cordys is neither liable for the proper and complete transmissio=
n of the information contained in this communication nor for any delay in i=
ts receipt. Cordys does not guarantee that the integrity of this communicat=
ion has been maintained nor that the communication is free of viruses, inte=
rceptions or interference. If you are not the intended recipient of this co=
mmunication please return the communication to the sender and delete and de=
stroy all copies.