You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by bu...@apache.org on 2004/07/09 17:56:01 UTC
DO NOT REPLY [Bug 29116] -
login usecase with emtpy referrer throws NPE
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29116>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29116
login usecase with emtpy referrer throws NPE
------- Additional Comments From ps@nomensa.com 2004-07-09 15:56 -------
in lenya/content/ac/login.xsp I commented out a bit of code:
/* FIXME: causes problems when no referrer
String
authenticatorId=(String)session.getAttribute("org.apache.lenya.cms.cocoon.acting.Authenticator.id");
String
authenticatorName=(String)session.getAttribute("org.apache.lenya.cms.cocoon.acting.Authenticator.name");
if(authenticatorId != null){
<authenticator><xsp:attribute
name="type"><xsp:expr>authenticatorId</xsp:expr></xsp:attribute>
<name><xsp:expr>authenticatorName</xsp:expr></name>
</authenticator>
}
else{
<no_authenticator_id_yet/>
}
String
protected_destination=(String)session.getAttribute("protected_destination");
if(protected_destination != null){
<xsp:content><protected_destination><xsp:expr>protected_destination</xsp:expr></protected_destination></xsp:content>
}
else{
<xsp:content><no_protected_destination/></xsp:content>
}
*/
and it seems to work with no referrer. This anything to do with fixing the
problem or have I opened myself up to a world of pain ?! Functionality seems to
be the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org