portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-396) Jetspeed portal doesn't work if client is behind Proxy/Firewall
Date Thu, 03 Nov 2005 18:06:47 GMT
    [ http://issues.apache.org/jira/browse/JS2-396?page=comments#action_12356709 ] 

Ate Douma commented on JS2-396:

I suggest you look in the jetspeed.log file under webapps/jetspeed/logs for possible clues.

Furthermore, enable access logging for Tomcat so you can see what requests are received by
To do so, put the following in your $CATALINA_HOME/conf/context.xml:

   <!-- standard access log configuration for all application Contexts-->
   <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
          prefix="localhost_access_log." suffix=".txt"

Note: the above works for Tomcat 5.5.12.

Then, compare the results of accessing Jetspeed locally and from behind your Proxy.

> Jetspeed portal doesn't work if client is behind Proxy/Firewall
> ---------------------------------------------------------------
>          Key: JS2-396
>          URL: http://issues.apache.org/jira/browse/JS2-396
>      Project: Jetspeed 2
>         Type: Bug
>  Environment: Server in Linux
>     Reporter: Bhaskar Roy

> I have installed Jetspeed2 M4 on Linux, it works fine if I access locally or from a PC
which is not behind Proxy, if the client is behind proxy, it doesn't work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message