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

form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • http-request-plugin
    • None

      I have a webapp deployed in my local tomcat configged with form auth and I'm trying to send a request using the http request plugin on Jenkins.
      I've added Form Authentication in the global configuration.

      Now I setup an job to send a request to get some info as response.

      But I keep getting 408 code as response.

      I had another try without the "j_security_check" suffix. The job can pass and get an 200 code, but the request wasn't successfully submitted and it's return a login page as response.

      Please kindly check and advice,
      Many thanks!

        1. another-try.jpg
          another-try.jpg
          46 kB
        2. build_console_output.jpg
          build_console_output.jpg
          79 kB
        3. global_auth.jpg
          global_auth.jpg
          27 kB
        4. job_config.jpg
          job_config.jpg
          46 kB

          [JENKINS-41726] form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response

          How long does it take to throw the error?

          Have you tried to increase the timeout configuration in the job?

           

          The only difference I saw from GET 200 to POST 208 is that 200 is using http://localhost:8080 and the other http://127.0.0.1:8080 . This shouldn't have difference unless you have a wrong configuration in hosts. Have you tried form with localhost instead of 127.0.0.1?

           

          Janario Oliveira added a comment - How long does it take to throw the error? Have you tried to increase the timeout configuration in the job?   The only difference I saw from GET 200 to POST 208 is that 200 is using http://localhost:8080  and the other http://127.0.0.1:8080  . This shouldn't have difference unless you have a wrong configuration in hosts. Have you tried form with localhost instead of 127.0.0.1?  

          Roger Lei added a comment -

          janario 

          Hi Janario, sorry for the late reply. I've tried both 127.0.0.1 and localhost. Almost got the error right after the job is running.

          I'm not sure if I've set the Form Authentication setting correctly under global configuration .

          I'm running on Jenkins1.610 with JDK version of 1.6. Does it require a higher version of Jenkins or JDK?

          Could you please advice if there's any document on how to setup and using this plugin?

          Roger Lei added a comment - janario   Hi Janario, sorry for the late reply. I've tried both 127.0.0.1 and localhost. Almost got the error right after the job is running. I'm not sure if I've set the Form Authentication setting correctly under global configuration . I'm running on Jenkins1.610 with JDK version of 1.6. Does it require a higher version of Jenkins or JDK? Could you please advice if there's any document on how to setup and using this plugin?

          The latest version requeries jdk1.7 and Jenkins 1.609.3

          Have you tried on this versions?

          You could try http://requestb.in/ (it is a service that show details to every request sent to it) to see what is been sent from the job execution.

          With that detail also try with 'curl'.

           

          We have a few documentation here http://wiki.jenkins-ci.org/display/JENKINS/HTTP+Request+Plugin

          Janario Oliveira added a comment - The latest version requeries jdk1.7 and Jenkins 1.609.3 Have you tried on this versions? You could try  http://requestb.in/  (it is a service that show details to every request sent to it) to see what is been sent from the job execution. With that detail also try with 'curl'.   We have a few documentation here http://wiki.jenkins-ci.org/display/JENKINS/HTTP+Request+Plugin

            janario Janario Oliveira
            unclerayray Roger Lei
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: