Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17347

xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • core
    • None

      The functions (ie `text()`) are broken in API's xpath.

      Example: https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text()

      Expected: "core_selenium-test"
      Actual: Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error.

          [JENKINS-17347] xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)

          Ivan Kurnosov added a comment -

          Guys, any plans for fixing this one?

          Ivan Kurnosov added a comment - Guys, any plans for fixing this one?

          benza added a comment -

          I am stuck with version 1.500 because of this bug.
          will it be fixed any time soon ?

          benza added a comment - I am stuck with version 1.500 because of this bug. will it be fixed any time soon ?

          twolfart added a comment -

          This looks like a dupliate of JENKINS-18116.

          twolfart added a comment - This looks like a dupliate of JENKINS-18116 .

          benza added a comment -

          Thanks twolfart!!
          setting hudson.model.Api.INSECURE=true works great

          benza added a comment - Thanks twolfart!! setting hudson.model.Api.INSECURE=true works great

          Daniel Beck added a comment -

          This issue is caused by the fix to a security issue, see the advisory. It also explains how to work around that problem. However, a better solution exists since 1.537 in Plugins providing an implementation of the SecureRequester interface, e.g.:

          https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin

          I'm resolving this as not a defect, because it's a deliberate change because of security concerns. That it shows a content decoding error instead of "Access Denied" is a different, less important issue.

          Daniel Beck added a comment - This issue is caused by the fix to a security issue, see the advisory . It also explains how to work around that problem. However, a better solution exists since 1.537 in Plugins providing an implementation of the SecureRequester interface, e.g.: https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin I'm resolving this as not a defect , because it's a deliberate change because of security concerns. That it shows a content decoding error instead of "Access Denied" is a different, less important issue.

            Unassigned Unassigned
            zerkms Ivan Kurnosov
            Votes:
            6 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: