Hi all, I have many complaints from users using my T4.1.2 application from behind some proxy servers. Basically, all JS/Ajax stuff gets broken. Unfortunately I don't have any proxied environment available here, and no way to build one (our web access is shared across several companies, and they wouldn't let me modify it for my tests).
So what I found closest to a proxy server for my tests is to use a web proxy (you know, one of those web sites that hide your IP and allow you to visit any site "anonymously"). I get the exact same broken behavior when I use one of those (I used http://www.webproxy.fr which is a french one, but I guess anyone would do). >From what I understand from the js errors, the problem relates to relative URLs used in some js calls. I think the web proxy replaces any URL that begins with my domain name by a proxied URL. It can't guess that the relative URL inside a js call is also to be proxied, resulting in attempts to retrieve js at the web proxy server root, which obviously do not work. This happens e.g. with the baseRelativePath parameter in djConfig or the registerModulePath call for tapestry dojo-related stuff. Just for you guys to be able to see it for yourself, I tried to access the time tracker demo app through the web proxy, and it also results in broken js. I'm not sure the problem is the same with proxy servers, so if there are any proxy expert around, I'd be very happy to hear from them ;-) Is there any way to work around this problem (like generating absolute URLs instead of those relative ones, but again, I don't know dojo enough to tell if this is feasable). Thx for any inputs Ch.
