Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0
    • Component/s: Core, SSL
    • Labels:

      Description

      The client can decipher the data only once it has received a full record over SSL. The record size can have significant impact on the page load time performance of the application. No limitation on record size means that clients might have to download up to 16KB of data before starting to process them, whereas very small records incur a larger overhead due to record framing. The suggestion is to configure the TLS record size to fit into a single TCP segment, this can improve page load times on browsers located over high latency or low bandwidth networks.
      ref: http://www.igvita.com/2013/10/24/optimizing-tls-record-size-and-buffering-latency/

        Attachments

        1. ssl_maxrecordsize.diff
          3 kB
          Wei Sun
        2. ssl_maxrecordsize2.diff
          4 kB
          Wei Sun
        3. TS-2365.diff
          3 kB
          James Peach

          Activity

            People

            • Assignee:
              jamespeach James Peach
              Reporter:
              sunwei Wei Sun
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: