[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-19 Thread rherr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42180  
 
 
  JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2017/Feb/19 8:00 PM  
 
 
Environment: 
 Jenkins 2.46 on Ubuntu 16.04.2 LTS, affects all browsers tested on OSX  
 
 
Labels: 
 configuration project  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 rherrick  
 

  
 
 
 
 

 
 I'm trying to configure a multiproject Gradle build on Jenkins 2.46. Anything that requires adding a panel is failing. For example, adding additional behaviors in SCM section fails, so I can't specify advanced submodules behaviors. I also can't add build or post-build actions. When I first load the configure page for the project, I get these errors (i.e. I'm not doing anything, just opening the project): 

 
configure:1 This page includes a password or credit card input in a non-secure context. A warning will be added to the URL bar in Chrome 56 (Jan 2017). For more information, see https://goo.gl/zmWq3m.
hudson-behavior.js:417 Uncaught TypeError: Cannot read property 'firstChild' of undefined
at registerValidator (/static/b7508750/scripts/hudson-behavior.js:417:66)
at Array.forEach (native)
at /static/b7508750/scripts/behavior.js:111:30
at Array.forEach (native)
at /static/b7508750/scripts/behavior.js:107:27
at Array.forEach (native)
at Object.applySubtree (/static/b7508750/scripts/behavior.js:93:17)
   

[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-20 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 Are you accessing Jenkins using a different URL than the one configured in Configure System? Are you using a reverse proxy and are you seeing a "broken reverse proxy" warning on the /manage URL?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-21 Thread rherr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 No, I'm using the same URL that's set in Configure System. I am using nginx in front of Jenkins running as a stand-alone application (i.e. not as a war in Tomcat), but I don't have the broken reverse proxy message. I just updated to 2.47, cleared my cookies and cache, and am still seeing the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-21 Thread rherr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 I can get things working again properly if I turn "Prevent Cross Site Request Forgery exploits" OFF on the "Configure Global Security" page. If I turn it on, the only option I have for "Crumb Algorithm" is "Default Crumb Issuer". So I select that and then it doesn't matter if I have "Enable proxy compatibility" checked or not, I see the same failure.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-21 Thread rherr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 In the nginx access logs, I see the following when I reload a project page: 

 
172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/a4338d24-8ef6-4b36-a45e-dba6f4b8139f/render HTTP/1.1" 403 305 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806"
172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/ab8ee004-37cc-4e2b-8d49-3802040cdf60/render HTTP/1.1" 403 304 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806" 

 Those are the only 403s I see on the page load, everything else is 200. There are no entries in the nginx error.log. In the jenkins.log, I get these messages: 

 
Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a.  Will check remaining parameters for a valid one...
Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /$stapler/bound/d29a127d-6455-4b93-80b3-653dc55aeaa7/render. Returning 403.
Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a.  Will check remaining parameters for a valid one...
Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /$stapler/bound/8ff58aec-9694-4c5f-b3a3-4906160a9176/render. Returning 403. 

 I can capture the full HTTP request/response cycle with Charles if that'd be helpful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 

ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a
 This is the same crumb concatenated into a list. That should not happen. Do you know any JS so you could look into what causes the crumb to be added twice here?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-22 Thread rherr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 rherrick commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 Yes, if you can give me some pointers on where to look. I've poked through it a bit and can see the crumb token getting added to the request headers but I'm not sure to look to see it being doubled up.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-02-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 prototype.js lines 1535-1541 is patching in the header. hudson-behavior.js 105 adds headers hudson-behavior.js 120 adds hidden form fields We're calling this the crumb (obviously) so looking for that in JS and your requests may help figure out what's going on.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2017-03-12 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-42180  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
 rherrick ping, we are waiting for the info from your side  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly

2019-02-16 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42180  
 
 
  JS errors and 403s prevent configuring project properly   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.