Raphaël Luta wrote ...
>
> "W. Craig Trader" wrote:
>
>> For security, I use a web proxy (Apache) sitting in my DMZ to proxy actual
>> page requests to internal web/app servers. Unfortunately, Jetspeed is
>> generating web pages that specifically reference the complete internal
>> server name/port ... so the resulting pages break the proxy.
>>
>> Is this a bug or a feature?
>> Is there a configuration parameter to override this behavior?
>> Where in the code should I look to patch this?
>>
>> Thanks for all of your work on Jetspeed, and for your time in answering my
>> questions.
>
> This is the default behavior of Turbine DynamicURI class which generates the
> URLs you see.
>
> The base HREF was a stop gap solution for 1.3a1 release and should not be actually
> useful anymore. It will be removed before next alpha.
>
> Configuring DynamicURI for generating absolute rather than external self-referencing
> links should be easy but I have not loooked into it yet (so you may have a go if you
> want :) ).
>
> I have the same kinds of issues than you in my production environment where there
> are DMZ and network load-balancers.
>
> So the short answer is: this is currently a known limitation that should be quite
> easy fo fix (see Turbine.DynamicURI) but it's not a current priority so if you need
> this soon, we'll gladly accept patches :)
Well, since I was trying to decide between Turbine and Jetspeed, and
the "feature" is in Turbine, I guess I'll have to dig around in Turbine
and see what I can come up with. Maybe this weekend, but more likely
next week some time.
It sounds like this should really be a configurable option: full or
partial URLs, instead of just a patch to replace the offending piece
of code.
Santiago Gala wrote:
>
> Raphaël Luta escribió:
>
> > This is the default behavior of Turbine DynamicURI class which generates the
> > URLs you see.
> >
> > The base HREF was a stop gap solution for 1.3a1 release and should not be actually
> > useful anymore. It will be removed before next alpha.
>
> Nevertheless, I know that phone.com WAP gateway needs the base. It is
> broken WRT resolving relative URLs. I suggest that the BASE (a good one,
> around the lines that you propose), is left as a configurable item, as I
> think most WAP services use Phone.com gateway.
>
> As an exmple, the URL
>
> http://fw.intranet.hisitech.com/c2/
>
> should show Cocoon2 homepage. It works in html and in WAP through the
> gateway translator. If you access it through (Movistar's) WAP Gateway,
> URLs in this page will show as broken cocoon resources, as the uri asked
> by the gateway is /cs/welcome/home.wml (for instance) instead of
> /c2/hello.wml It works with the emulators I have tested.
>
> 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.
This is a good idea, but if I have Apache configured to serve up images
and raw files, and Tomcat/Turbine/Jetspeed serving up web pages, then I
have to partition the entire application into "JSP/Servlets" and "Other
stuff" and manage distributing the pieces to separate servers. Bad.
> Nevertheless, there are broken things in the BASE calculation/handling
> now.
Again, this looks like it needs to be configurable, instead of simply
coded one way or another.
- Craig -
--
============= Excellence is a journey, not a destination =============
=============== W. Craig Trader <[EMAIL PROTECTED]> ===============
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
