request: control of chunk size and forcing Transfer-Encoding chunked

Discussion in 'Feedback/Feature Requests' started by aww, May 11, 2010.

  1. aww

    aww Well-Known Member

    I would like to be able to fine tune the chunk size that is using when sending gzip compressed content.

    By the way, is it PHP or Litespeed that triggers when something is being chunked in the first place?

    I noticed that static content is NEVER chunked only PHP.

    Is it possible to give us a feature to control chunking for static content and also what size chunk?

    The idea behind this is to force browsers to start rendering sooner instead of having to wait for the entire file.
  2. mistwang

    mistwang LiteSpeed Staff

    chunked encoding cannot be control in any way.
  3. aww

    aww Well-Known Member

    Nginx appears to somehow send static content as chunked.

    Here is an example:
    examine the headers to see

    Is it not possible to enhance litespeed to do the same?

    I guess I could pass all content through PHP to force chunking but that would make it lose last modified, etag, etc. unless I added PHP code to calculate that in the headers, which would be a lot of overkill.
  4. mistwang

    mistwang LiteSpeed Staff

    Chunked encoding should be avoided when possible, it is slow.
    And I doubt it will make the page rendered faster over regular response with content-length header.

Share This Page