Pipeline compilation error detection broken when using CSRF detection

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Due to use of what seems to be an atypical AJAX call, when you are running Jenkins with CSRF defense enabled (i.e., typical secured installation), the syntax error display from JENKINS-32067 does not work: the server rejects the POST request for lacking a crumb.

      Typical use of Ajax from prototype works because of this.

            Assignee:
            Antonio Muñiz
            Reporter:
            Jesse Glick
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: