At 17:12 2000-12-14, Santiago Gala wrote:
> > -----Mensaje original-----
> > De: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]En nombre de
> > [EMAIL PROTECTED]
> > Enviado el: jueves, 14 de diciembre de 2000 11:55
> > Para: JetSpeed
> > Asunto: Re: How do we want to handle links to images?
> >
> >
> > ingo schuster wrote:
> > >
> > > Hi,
> > >
> > > I found the root of our (/)images problem:
> > >
> > > The ECS layout uses a <base> tag, the JSP layout didn't. That's why
> > > "images/max.gif" worked well with ecs but not with JSPs (and why I used
> > > absolute links to the images). These absolute links are fine as
> > long as you
> > > run jetspeed in the default web application "/", but they don't
> > work with a
> > > own jetspeed application (e.g. "/jetspeed/"). That's how Mike
> > seems to have
> > > his jetspeed configured.
> > > Anyway, not that the problem is clear, it's easy to fix: I changed all
> > > "/images" paths to "images" and I will add a <base> tag to the
> > desfault.jsp.
> > >
> >
> > You're right. Actually, I sent an email about this yesterday but
> > it did not
> > seem to have reached the mailing-list for some reason, so here it
> > is again:
> >
> > Yes, I chenged the semantics of the images and external content
> > links in the JR.p
> > and java code:
> >
> > In the current version, the images/css etc are resolved like this in ECS:
> >
> > http://<servername>:<serverport><contextname><content_root_url><im
>age href>
>
>
>There are two news, one good and one bad :-)
>
>The good one is that Tomcat 3.2 final works with SSL out of the box (you
>need to download additional SSL support, but that's all). We tested it and
>it works great!
>
>The bad one is that the static reference to "http" in the base breaks images
>under "https". We need to have something similar to a
>DynamicURI.getProtocol() to handle this.
>
>
>It worked properly under the previous scheme, but it is broken now. I think
>using <BASE> is not a good idea but, if we use it, it should be calculated
>afresh for each request, as
><protocol>://<servername>:<serverport><contextname>...
>
>
Santiago,
please remember that links with hardcoded servernames won't work when a
gateway is used:
1st Request: Client ---> Gateway ---> PortalServer
Clinet ---> Gateway <--- PortalServer
The response contains links like "http://<PortalServer>/jetspeed"
The 2nd Request cant pass the Firewall as it addreeses the PortalServer
directly!
Client --------->| PortalServer
Firewall
ingo.
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
>Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
