-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/6/11 3:09 PM, André Warnier wrote:
> In fact, does anyone in this Tomcat world really know exactly why
> no standardisation committee or group of experts has yet come up
> with an RFC for HTTP 2.0 and an RFC for HTML 10.0 (or whatever the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 12/6/11 12:06 PM, Konstantin Kolinko wrote:
> 2011/12/6 Christopher Schultz :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Konstantin,
>>
>> On 12/6/11 11:15 AM, Konstantin Kolinko wrote:
>>> 1. I do not use valves that call
Christopher Schultz wrote:
...
Honestly, the whole world should just set everything to UTF-8 and move
on with life :)
+5
In fact, does anyone in this Tomcat world really know exactly why no standardisation
committee or group of experts has yet come up with an RFC for HTTP 2.0 and an RFC for H
2011/12/6 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Konstantin,
>
> On 12/6/11 11:15 AM, Konstantin Kolinko wrote:
>> 1. I do not use valves that call getParameter(), so I have not
>> seen the need, but the FormAuthenticator will need the feature?
>
> ExtendedAcces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 12/6/11 11:15 AM, Konstantin Kolinko wrote:
> 1. I do not use valves that call getParameter(), so I have not
> seen the need, but the FormAuthenticator will need the feature?
ExtendedAccessLogValve can also cause the query string to be
2011/12/6 Christopher Schultz :
> On 12/4/11 8:02 PM, Konstantin Kolinko wrote:
>> Make sure that content type and charset value in a) Content-Type
>> HTTP header sent by server and b) in META tag in HTML text have
>> _literally_ the same value. If they both are present and they do
>> not match, od
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 12/5/11 6:53 PM, Konstantin Kolinko wrote:
> Note, that there is standard "SetCharacterEncodingFilter" in Tomcat
> 7. (In 7.0 it is in o.a.c.filters package, in 6.0 and 5.5 it is
> examples webapp).
I see that you've moved that out of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 12/4/11 8:02 PM, Konstantin Kolinko wrote:
> Make sure that content type and charset value in a) Content-Type
> HTTP header sent by server and b) in META tag in HTML text have
> _literally_ the same value. If they both are present and t
2011/12/6 André Warnier :
> Marvin Addison wrote:
>>>
>>> /can/ the servlet (or one of the filters)
>>> do anything that would cause the value of "name1" to /not/ be a correct
>>> Java
>>> "TÜV" string in the servlet ?
>>
>>
>> Yes, absolutely. If this is a posted value and some filter fires that
Marvin Addison wrote:
/can/ the servlet (or one of the filters)
do anything that would cause the value of "name1" to /not/ be a correct Java
"TÜV" string in the servlet ?
Yes, absolutely. If this is a posted value and some filter fires that
coerces the encoding (e.g. request.getParameter() in
> /can/ the servlet (or one of the filters)
> do anything that would cause the value of "name1" to /not/ be a correct Java
> "TÜV" string in the servlet ?
Yes, absolutely. If this is a posted value and some filter fires that
coerces the encoding (e.g. request.getParameter() in the case of POST)
o
2011/12/5 André Warnier :
> Hi.
>
> I need help with a problem on a Tomcat system. The system is of difficult
> access, and I cannot access it directly right now (this is Sunday night in
> Europe).
> I know that the system runs Tomcat 6.something, under Oracle/Sun Java 1.6,
> and that's all I can
Hi.
I need help with a problem on a Tomcat system. The system is of difficult access, and I
cannot access it directly right now (this is Sunday night in Europe).
I know that the system runs Tomcat 6.something, under Oracle/Sun Java 1.6, and that's all
I can say right now. The platform is RedHa
13 matches
Mail list logo
