SEC-1111: DefaultLoginPageGeneratingFilter does not work with messages_ko_KR.properties #1362

Closed
spring-issuemaster opened this Issue Feb 24, 2009 · 1 comment

1 participant

@spring-issuemaster

Shin Sang Jae (Migrated from SEC-1111) said:

(attachement is eclipse project and screenshot)

I made messages_ko_KR.properties.
(C:\workspace\codelabor-spring-security-template\src\main\resources\org\springframework\security\messages_ko_KR.properties)

And I try default form-login with empty username and password.
500 Error occures like screenshot image.
-—————————————————————————————————
java.io.CharConversionException: Not an ISO 8859-1 character: 비
at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:89)
-—————————————————————————————————

I retry login with correct username and password.
Login is sucess.
In index.jsp page, I test messageSource like this:
-———————————————————————————————————
WebApplicationContext context = WebApplicationContextUtils.getRequiredWebApplicationContext(application);
MessageSource messageSource = (MessageSource) context.getBean(“messageSource”);
out.println(messageSource.getMessage(“AbstractUserDetailsAuthenticationProvider.badCredentials”, null, Locale.getDefault()));
-———————————————————————————————————
index.jsp page works, like attachement image.
So my message_ko_KR.properties is good.

What’s wroing with DefaultLoginPageGeneratingFilter?

@spring-issuemaster

Luke Taylor said:

Looks like the problem was due to not using response.getWriter(). Printing directly to the ServletOutputStream doesn’t appear to encode the data properly.

@spring-issuemaster spring-issuemaster added this to the 3.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment