Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-3304

server push doubles the auto-timeout delay

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Normal Normal
    • 8.0.3
    • 8.0.2
    • ZK Client Engine
    • Security Level: Jimmy
    • None
    • tested with Servlet 3 Comet Server Push

      steps to reproduce

      configure automatic timeout and a timeout page

      	<session-config>
      		<automatic-timeout />
      		<timeout-uri>/timeout.zul</timeout-uri>
      		<timer-keep-alive>false</timer-keep-alive>
      	</session-config>
      

      and run the attached examples, which both use a timeout of 12 seconds

      actual result

      timeout-redirect-noSP.zul -> times out/redirects after 17 seconds (12+5 seconds)

      timeout-redirect.zul -> times out after 17 seconds (SP gets stopped) and redirects after another 17 seconds

      expected result

      both pages should redirect after the same time ~17seconds

      debug info

      in a working case after the timeout the client side sends a "dummy" request to the server which responds with a header ZK-Error=410 resulting in the timeout redirect.

      when using the server push the "dummy" request doesn't respond with a 410 ZK-error header, which results in a call to zAu._resetTimeout() in au.js Line177 ; extending the session.
      Still the server push is stopped correctly at client side

      root cause

      something at server side misses to set the 410 response header when the server push is active so that the client engine waits twice as long before redirecting

        1. network-noSP.png
          network-noSP.png
          36 kB
        2. network-withSP.png
          network-withSP.png
          56 kB
        3. timeout-redirect.zul
          0.4 kB
        4. timeout-redirect-noSP.zul
          0.1 kB

            SEFI SEFI
            cor3000 cor3000
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day
                1d