Hi Fred,
RIFE never sets that explicitly, I think the servlet container does
so. Which clients have problems with that?
From the HTTP/1.1 spec:
"All HTTP/1.1 applications MUST be able to receive and decode the
"chunked" transfer-coding, and MUST ignore chunk-extension extensions
they do not understand."
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html)
Do you set the "GZIP_COMPRESSION" configuration parameter? If so, you
could try disabling it by setting it to 'false', maybe that's what
adds the header.
Best regards,
Geert
On 1-dec-05, at 13:59, F Baube wrote:
Rife insists on adding a header "Transfer-Encoding: chunked".
If I try calls to
setHeader("Transfer-Encoding", null);
or
setHeader("Transfer-Encoding", "");
sometimes it sets this header to an empty string.
other times it adds a second, empty header of this
name, but also leaves in place the one that says
"Transfer-Encoding: chunked".
this is creating problems on the client side.
Is there some way to suppress the addition
of the header "Transfer-Encoding: chunked" ?
thx
fred
--
F.Baube *
Georgetown/MSFS/1988 * Act locally.
email fbaube#welho.com * Think pangalactically.
gsm +358 41 536 8192 *
wmd 60°11'10.8"N 24°57'36.9"E
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
