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

No preemptive authentication

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • http-request-plugin
    • None
    • Jenkins 1.590. HTTP Request Plugin 1.8.6

      Some servers doesn't send a authentication challange response (401), so the authentication header is not sent in the next request attempt (default behaviour in the Apache Commons Http Client).
      To send always the authentication header, the preemptive authentication must be enabled. In the case of Apache Commons Http Client, the AuthCache must be present in the HttpContext. I attached a patch that solves this.

            janario Janario Oliveira
            anloci Angel López Cima
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: