Herman, Thanks for the feedback. See comments below.
Randy On Sat, 2005-12-17 at 11:23 +0100, Herman Reintke wrote: > LS, > > I am using the binary J2 installation with the Derbydatabase. On top of that > an Apache webserver is installed to be able to access the J2 Portal, together > with my other installs/pages using port 80. > > This all workes but I found some specific issues with the installation. > > 1/ access path. > There are (at least) two paths you need to define. 1/ Jetspeed (as expected) > but also 2/ j2-admin. > The j2-admin path is acessed directly from ouitside and I had to configure > the proxy to pass thru to the jetspeed tomcat. > Questions : > - Are there any other paths required ? > - When will a separate path be used/needed ? Given that the different portlets and their associated application code are deployed in webapps, I believe that it is always possible that these webapps are accessed directly. It is then safest to add paths to all deployed Jetspeed webapps in the Tomcat webapps directory. > > 2/ Caching > Sometimes I only have access to my J2 environment from behind a proxyserver. > With the standard install I noticed several occasions when I got "old pages" > which were only refreshed to the correct onces after a "forced" get by the > browser. I only checked a few pages pages but the most obvious were : > - main page, I regulary got the "admin logged in page" instead of the > anonymous page where youneed to login. > - Portal site manager > When working with the PSM The portal site browser and portal site detail are > not updated when selecting. > I've come around this behaviour nor to forcing all responses to have the > directive "cache-control no-cache'. > Checking the apache access log I see for example the portal site detail alway > being requested as : GET > /jetspeed/portal/_ns:YXBkYi0xfGMwfGQwfGY_/Administrative/site.psml, which > indeed would allow a proxyserver to serve cached content. > Question : > - Are there any specific cache-control options to be set in J2 ? I am not aware of any global configurations that can be set to add headers to all outgoing responses. Have you been able to verify that all is well without the proxyserver in place? These appear to be the only headers added for pages: Set-Cookie: JSESSIONID=F5B35CB1E279026157BF0267A9176BC3; Path=/jetspeed Content-Type: text/html;charset=UTF-8 Date: Sat, 17 Dec 2005 15:28:46 GMT Server: Apache-Coyote/1.1 Connection: close IMO, we should be adding the HTTP 1.0 "expires: 0" and HTTP 1.1 "cache-control: nocache" headers on all portal page responses. I will consider getting this added for the 2.01 release that is currently pending. Of course, the team will need to vote on this inclusion. > > 3/ 404 errors > I see a number of pages not returned by the J2 environment > "GET /jetspeed/decorations/layout/css/data-scoller.css HTTP/1.1" 404 1099 > "GET /jetspeed/decorations/portlet/tigris/images/nw_maj_rond.gif HTTP/1.1" > 404 1129 > Maybe they are missging from the install Both of these files should exist, but may not be being located properly under all circumstances. Can you send a copy of your access log to me directly? Meanwhile, I'll be looking for similar occurrences here. > > If more info needed please let me know. > > Kind regards, > > Herman Reintke --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
