with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkp7KysACgkQ9CaO5/Lv0PAXYACePgJvGnixOxA1zrBmm1ZAcgc1
> uHkAnA/QdvJE5xPQCC78Y9q4wb+llmwP
> =5g5F
> -END PGP SIGNATURE-
>
> -----
> To unsubscr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keyur,
On 8/6/2009 12:35 PM, Keyur Shah wrote:
> While headers can never be added as headers once the response is committed,
> the trailer headers are in fact encoded in the body itself.
>
> So the convention could be that if a user has specified ce
André Warnier wrote:
> Michael Ludwig wrote:
>> Christopher Schultz schrieb:
>>
>>> When chunked encoding is being used, HTTP allows you to include
>>> "headers" after the response by including a "final chunk" with more
>>> headers for the previous chunk.
>>
> I am well aware of that, at the HTTP l
ttp://enigmail.mozdev.org/
>
> iEYEARECAAYFAkp68DcACgkQ9CaO5/Lv0PA1cwCcDeQZ8fGbMlbAP4JR0L7lBAE9
> ZCcAoIxtcTbIivWrEP84qtfMoGjsYSwF
> =tMQw
> -END PGP SIGNATURE-
>
> -------------
> To unsubscribe, e-mail: users-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
On 8/6/2009 10:08 AM, Michael Ludwig wrote:
> Christopher Schultz schrieb:
>
>> When chunked encoding is being used, HTTP allows you to include
>> "headers" after the response by including a "final chunk" with more
>> headers for the previou
Michael Ludwig wrote:
Christopher Schultz schrieb:
When chunked encoding is being used, HTTP allows you to include
"headers" after the response by including a "final chunk" with more
headers for the previous chunk.
I am well aware of that, at the HTTP level.
However, the Servlet Spec seems t
Christopher Schultz schrieb:
When chunked encoding is being used, HTTP allows you to include
"headers" after the response by including a "final chunk" with more
headers for the previous chunk.
So those traling headers are actually footers.
The headers you want in this chunk should be mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 8/5/2009 7:09 PM, André Warnier wrote:
> Servlet Specification 2.4, SRV 5.2, Headers :
>
> "To be successfully transmitted back to the client, headers must be set
> before the response is committed. Headers set after the response is
> commi
Keyur,
I think what Filip was trying to tell you is this :
Servlet Specification 2.4, SRV 5.2, Headers :
"To be successfully transmitted back to the client, headers must be set
before the response is committed. Headers set after the response is
committed will be ignored by the servlet contain
u la
> copie de ceci est interdite. Ce message sert à l'information seulement et
> n'aura pas n'importe quel effet légalement obligatoire. Étant donné que
> les email peuvent facilement être sujets à la manipulation, nous ne
> pouvons accepter aucune responsabilit
re sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Wed, 5 Aug 2009 14:55:35 -0700
> From: keyu...@gmail.com
> To: users@tomcat.apache.org
> Subject: Re: Trailer header and tomcat
>
>
> Thanks Filip. Buffering is wha
he header, write the response
>
> Filip
>> Thanks,
>> Keyur
>>
>
>
> -------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional co
On 08/05/2009 02:14 PM, Keyur Shah wrote:
Tomcat by default sends chunked responses => Transfer-Encoding:chunked
I'm calculating the ETag for the response dynamically as the content is
being
written to the response stream. Since I'll know the final value of the ETag
only
when the stream is clos
nks,
Keyur
--
View this message in context:
http://www.nabble.com/Trailer-header-and-tomcat-tp24835409p24835409.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.a
14 matches
Mail list logo
