You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/02/02 17:24:14 UTC

[jira] [Updated] (TS-2365) Configure max TLS record size

     [ https://issues.apache.org/jira/browse/TS-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-2365:
------------------------------

    Issue Type: New Feature  (was: Improvement)

> Configure max TLS record size
> -----------------------------
>
>                 Key: TS-2365
>                 URL: https://issues.apache.org/jira/browse/TS-2365
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Core, SSL
>            Reporter: Wei Sun
>            Assignee: James Peach
>              Labels: A
>             Fix For: 4.2.0
>
>         Attachments: TS-2365.diff, ssl_maxrecordsize.diff, ssl_maxrecordsize2.diff
>
>
> 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/



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)