Ours is an SSL site. Like I wrote I just sue the absolute file path below.
It works for all the Unix boxes. PDF imbeds the image anyway, rather than just linking to it and letting the browser server it up like HTML does. So you shouldn't see that secure-to-insecure error. Todd McGrath wrote: > > Will this work for SSL sites? > > I have servlets that produce images (graphs) and I'm try to include them in > the generated PDFs. I wasn't sure that you could use relative path for > "src" attribute? Since I wasn't able to get it working, I needed to create > a separate site in order to use absolute path to servlets (example: > http://localhost/Pie, where Pie is the graph producing servlet) Obviously, > I would like to use relative so users do not see pop-up message about "not > secure" > > Is anyone using FOP in SSL enabled sites with external-graphic that are not > static filebased? > > Todd > > -----Original Message----- > From: Max Froumentin [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 03, 2001 10:26 AM > To: [EMAIL PROTECTED] > Subject: Re: fo:external-graphic question > > You wrote: > > > If you want a relative URI, why not just use a relative URI? I.e., > > > src="config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLogoGreenBi > g.gif"? > > Then the current protocol, host, and directory will be used as the base > URI > > and the relative URI interpreted relative to that. > > And of course this should ideally be > > src="url(config/isappdev...)" > > Max. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
