That bugzilla issue only addresses filters, not character encoding, with
j_security_check.
On the one hand the servlet 2.4 spec actually addresses response
character encoding issues nicely, with the addition of stuff like:
locale-encoding-mapping-list
locale-encoding-mapping
See the tomcat-dev list archives, there are conversations about that now.
(or the last day or 2)
-Tim
Adam Hardy wrote:
Do you know when the 2.4 spec goes final?
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Joerg Heinicke [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Tim Funk wrote:
You can't intercept j_security_check with a filter, it violates the
spec.
-Tim
This is at least one answer to my thread started last week:
http://www.mail-archive.com/[EMAIL
Did that alrady. Here's the gory details and the conclusion is valid for 4
and 5. It seems the spec folks took care of the character encoding issue but
forgot how to fix it for j_security_check. So the short term solution is
probably a custom solution per platform. :( (Maybe google has the
Thanks for the replies.
So this means I have to go with custom realm and authenticator? Actually I first tried
with them but got stuck, I guess I was quite close to success though. I posted one
article asking for help several days ago but got no response at all. I am reposting it
below,
Dear All,
I wrote a filter servlet that does some preprocessing. Basically it intercepts the
call of j_secuity_check. The problem is that most of the time it was just bypassed.
The only way to trigger it as I found is to first fill the form and got authenticated,
then go back and try the
You can't intercept j_security_check with a filter, it violates the spec.
-Tim
Lawence wrote:
Dear All,
I wrote a filter servlet that does some preprocessing. Basically it intercepts the call of j_secuity_check. The problem is that most of the time it was just bypassed. The only way to
Tim Funk wrote:
You can't intercept j_security_check with a filter, it violates the spec.
-Tim
This is at least one answer to my thread started last week:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg104931.html.
What are the consequences/possibilities to set the request character
encoding
Honestly, I personally have no clue with respect to encoding issues. I will
be playing with UTF-8 soon but ala, I am stuck in ISO8859-1 for now.
But my gut feel is container authentication implementation is purely
container dependent. So you'll be stuck with tomcat, or weblogic, or ???.
