RE: Problems with chunked encoding

Hi,
I had the same problems.
Some SonyEricsson HTTP protocol implementations use "Transfer-Encoding:
chunked" to post MMS. In case with Apache http server i got a
HTTP_LENGTH_REQUIRED 411.
This is why, because according to
http://httpd.apache.org/docs/misc/client_block_api.html, Apache delegates to
solve how to read client input to other application level modules
(mod_cgi,mod_perl,mod_php,etc...), and none of them intend to produce
"Transfer-Encoding: chunked".

To solve this i was forced to write mod_dechunk apache module, which acts
with request on more early stage them other modules and produce http posts
with "Transfer-Encoding: chunked". It collects chunks, writes combined data
to temporary file, set environment variable DECHUNKED_FILE with value of
path to temp file, and delete temp file on
apache request cleanup. Using together, other modules
(mod_cgi,mod_perl,mod_php,etc...) can determine this case
(Transfer-Encoding: chunked) finding environment variable DECHUNKED_FILE,
and obtain posted data from file locating variable value.



> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]]On Behalf Of Mindaugas Riauba
> Sent: Wednesday, June 22, 2005 2:32 PM
> To: [email protected]
> Subject: Problems with chunked encoding
> 
> 
> 
>   Hello,
> 
>   It looks like kannel has some problems with chunked encoding.
> Of course about chunking is just guess.
> 
>   The problems appears when we try to use kannel for MMSes. New
> SonyEricsson phones can be switched to use either HTTP or WAP
> to submit MMSes. And in http mode we had quite a few problems
> because e.g. SE500 uses chunked encoding to submit messages. Many
> programs were quite surprised to find chunked encoding going
> client->server not server->client. :)
> 
>   I'm blaming kannel because MMS when sent in HTTP mode goes
> phone->proxy->MMSC and is OK. When in WAP mode it goes
> phone->kannel->proxy(the same)->MMSC.
>   Maybe kannel is passing only one chunk? Because I'm sending
> ~8kb MMS and proxy receives 'Content-length: 2306' HTTP POST.
> So obviously something is lost.
> 
>   What to do or how to track problem more precisely?
> 
>   Thanks,
> 
>   Mindaugas
> 
>