Just to repeat what I stated in the ticket:
The problem I have with the suggested approach is that it treats UTF-8
as an
exception, rather that a norm for my whole application server. I am
not sure
that I should be having to be specifying the encoding before handling
every
request. For a we
Jr. wrote:
Andre-John Mas wrote:
Just to repeat what I stated in the ticket:
The problem I have with the suggested approach is that it treats
UTF-8
as an
exception, rather that a norm for my whole application server. I am
not
sure
that I should be having to be specifying the encoding before
On 7-Oct-08, at 07:02 , Mark Thomas wrote:
Andre-John Mas wrote:
Thanks for the answer on this point. Reading section 3.7.1 of RFC
2616
indicates that request can specify a character other than the
default.
For this reason the following should technically be legal:
What I see, from
