Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-7529

Web scenario login don't work correctly

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 2.2.2
    • Templates (T)
    • None
    • CentOS release 6.4 (Final) (only zabbix server)

      I have created a scenario. When I configure the first step, the url that I have configured in scenario obtains a response code 200 but the real response code must will be 302 because this URL is redirect to login page: (see result with curl)

      curl -v "http://IP/sscreen/index.php"

      • About to connect() to IP port X (#X)
      • Trying IP... connected
      • Connected to IP (IP)port X (#X)
        > GET /sscreen/index.php HTTP/1.1
        > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.6.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
        > Host: IP
        > Accept: /
        >
        < HTTP/1.1 302 Found
        < Date: Thu, 12 Dec 2013 12:40:18 GMT
        < Server: Apache/2.2.15 (CentOS)
        < X-Powered-By: PHP/5.3.3
        < Set-Cookie: PHPSESSID=3l4ltg7cj7hl7ie7qj5p9jnsf2; path=/
        < Expires: Thu, 19 Nov 1981 08:52:00 GMT
        < Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
        < Pragma: no-cache
        < Location: http://IP/sscreen/login.php?&er=1
        < Content-Length: 1267
        < Connection: close
        < Content-Type: text/html; charset=UTF-8
        <
        <html>
        <head>
        <meta htt.........

      By the way, I try too, to configure the first step with login page and to do the login, but obtains the response code 200 and the login doesn't work because in step 2 I check another URL of same web and doesn't obtains the content that I request on step.

      Please, can tell me how to do a login web scenario?

      Many thanks

            Unassigned Unassigned
            noc imagina
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: