ingo schuster wrote:
>
> At 10:20 02/01/01, Raphaël Luta wrote:
> >Santiago Gala wrote:
> > >
> > > In my setup, using NAT and mod_jk, current Jetspeed is working right. I
> > > think that if your reverse proxy is Apache, you could configure it to
> > > connect to Jetspeed using APJ12/APJ13 connectors (that can be remote if
> > > you want), and your problems will disappear.
> > >
> >
> >As long as your HTTP server runs on the same port that its NAT counterpart,
> >it's OK. If you do port translation as well, you need to customize the
> >DynamicURI as the server has *no reliable, secure way* of guessing the port
> >the client used to connect.
>
> What about using turbine's RelativeDynamicUri? It does exactly the same as
> DynamicUri only that it doesn't specify protocol, server and port - The
> client will so reuse the server name that it used for the previous request.
> We had exactly the same problem and with RelativeDynamicUri it works well.
>
> Is there any reason to specify protocol, server name and port in our URLs?
> I would propose to generally use RelativeDynamicUri instead of DynamicUri
> within Jestpeed.
>
+1
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
