Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: transfer-encoding:chunked |
|
| Author |
|
virtom
Joined: 15 Jul 2009
Posts: 1
|
 Posted: Wed 15 Jul '09 8:56 Post subject: transfer-encoding:chunked |
 |
|
I have a client application that can't work with transfer-encoding:chunked header.
Can Apache help me to decode chunked message?
Here is http://mail-archives.apache.org/mod_mbox/httpd-cvs/200012.mbox/%3C20001212213513.13990.qmail@locus.apache.org%3E some info that apache can dechunk.
| Quote: | Compute the content length (and add appropriate header field) for
the response when no content length is available and we can't use chunked encoding. [Jeff Trawick] |
But I can't understand how to use it. I'm newbie with apache |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7355
Location: Germany, Next to Hamburg
|
| Posted: Fri 17 Jul '09 10:04 Post subject: |
|
|
ee RFC 2616. Using either the Content-Length header OR chunked encoding
is a MUST in HTTP 1.1.
Something different is using HTTP 1.0.
The only (HTTP) ways of sending an unknown length file are:
a) Using HTTP 1.0, and closing the connection at the end (but the client
cannot know for sure that the file end has arrived, and I am not even
sure it is standards compliant).
b) Using HTTP 1.1, and using chunked encoding.
Unfortunately, you will either need to disable keep-alive and gzip / deflate or you will need to rework your client. |
|
| Back to top |
|
|
|
|
|
|
