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] Updated: (JS2-828) HTTP 403 immediately after login in Tomcat 5.5.25.
Date Thu, 13 Dec 2007 03:22:44 GMT

     [ https://issues.apache.org/jira/browse/JS2-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ate Douma updated JS2-828:
--------------------------

        Fix Version/s:     (was: 2.1.3)
                           (was: 2.2)
          Environment: Tomcat >= 5.5.24  (was: Linux, Tomcat 5.5.25, JDK5. jetspeed 2.1.3-dev
branch)
    Affects Version/s:     (was: 2.1.3)
                           (was: 2.2)

> HTTP 403 immediately after login in Tomcat 5.5.25.
> --------------------------------------------------
>
>                 Key: JS2-828
>                 URL: https://issues.apache.org/jira/browse/JS2-828
>             Project: Jetspeed 2
>          Issue Type: Bug
>         Environment: Tomcat >= 5.5.24
>            Reporter: Mohan Kannapareddy
>            Assignee: Ate Douma
>            Priority: Critical
>
> Immediately after logging into the portal, the URL address box in the browser displays:
>  http://localhost:20000/jetspeed/login/redirector
> ======================
> And the page displays:
> HTTP Status 403 - Access to the requested resource has been denied
> type Status report
> message Access to the requested resource has been denied
> description Access to the specified resource (Access to the requested resource has been
denied) has been forbidden.
> Apache Tomcat/5.5.25
> ======================
> I believe this is the same behavior in Tomcat 6.0.x and I get the same thing in GlassFish
v2-b58g.
> This does *NOT* happen in Tomcat 5.5.23 or lower versions. Something changed between
5.5.23 and 5.5.25.
> Also, after the login post if you just type in the URL http://<>/jetspeed, the
page appears normally and you can
> function.
> I do not know whether it is relevant but at least GlassFish appears to record the following
in the server.log.
> Unable to set request character encoding to UTF-8 from context /jetspeed, because request
parameters have already been read, or ServletRequest.getReader() has already been called

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message