[JIRA] [core] (JENKINS-31618) loginLink.jelly JellyTagException

[pjano...@redhat.com (JIRA)]

Title: Message Title

Pavel Janoušek commented on JENKINS-31618   Re: loginLink.jelly JellyTagException The whole CLI is affected as well. I'm a bit curious because I'm aware of two different scenarios with completely different result. I. If I use a JENKINS_HOME from the past (let's say rolling for a year), I can't hit this issue. II. If I use a completely clean JENKINS_HOME instance (the best is a new directory, start Jenkins from the war (JENKINS_HOME=newdir java -jar jenkins.war) and follow the Jenkins install wizard), this issue manifests itself. If I forced the argument type to java.lang.String, method encode(String, String) has found but NPE occurred because the first String input parameter was null. The question is why is the result of _expression_: ${if (request.session.attribute('from')!=null) request.session.getAttribute('from'); else if (request.getParameter('from')!=null) request.getParameter('from'); else if (request.requestURI=='/loginError' || request.requestURI=='/login') '/'; else request.requestURI; is null in the case of the completely new clean Jenkins instance. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.