Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1913

apply ReadTimeoutStreamSourceConduit/WriteTimeoutStreamSinkConduit also on the UndertowClient side if READ_TIMEOUT/WRITE_TIMEOUT options are set

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 2.2.13.Final, 2.0.42.Final
    • 2.2.8.Final
    • Core
    • None

      Currently if READ_TIMEOUT/WRITE_TIMEOUT options are set on the server side, the ReadTimeoutStreamSourceConduit/WriteTimeoutStreamSinkConduit wrappers will be used(like in HttpOpenListener.java), so the READ_TIMEOUT/WRITE_TIMEOUT works from the server side point of view. However, client side will ignore READ_TIMEOUT/WRITE_TIMEOUT options setting. I think client side should have similar implementation as the server side.

      Think this scenario, Undertow client has READ_TIMEOUT option set as 600ms,and send a GET request to the Server, while server somehow only return response after 2000ms. In this case Undertow client should just stop waiting after 600ms and close the connection, while currently the client still waits over 600ms until server returns a response

            flaviarnn Flavia Rainone
            yfang@redhat.com Freeman(Yue) Fang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: