Hi all,
I have unique problem here
Little background here
My application runs in 74 countries
It s a J2EE application based on Struts Jsp Hibernate
Our application has 2 users from london, when they try to do a sql search function it throws up the error
But, other users from the different countries are able to do it..
conflicts.intranet.standardchartered.com : potentially vulnerable to CVE-2009-3555- this is the message that is shown in error console of mozilla
Can you help??
There are two different issues here, the known vulnerability, and the missing S2 result.
That S2 is trying to find an "input" result means that validation (or type conversion, perhaps on the dates?) has failed. Without knowing more it's impossible to help.
Did you try URL-encoding the link?
sankey jain
Ranch Hand
Joined: Apr 29, 2010
Posts: 58
posted
0
David Newton wrote:There are two different issues here, the known vulnerability, and the missing S2 result.
That S2 is trying to find an "input" result means that validation (or type conversion, perhaps on the dates?) has failed. Without knowing more it's impossible to help.
Did you try URL-encoding the link?
Hi david,
but, this works for all the other users across the world. i have tried executing the same functionality with people from dubai,Singapore etc.
it works jsut fine !!
Funny thing, this is what i did.
i have this application hosted on my local as well.
i gave the London user url of my local apache/tomcat and asked her to access the same function
she was unable to do it
but, i was able to do it from my laptop
i am guessing a browser issue, and when you say more information, what is required?
will be more than happy to post it up
Turn on devMode, set logging to DEBUG, and find out why it's looking for the "input" result.
sankey jain
Ranch Hand
Joined: Apr 29, 2010
Posts: 58
posted
0
David Newton wrote:Turn on devMode, set logging to DEBUG, and find out why it's looking for the "input" result.
issue resolved, it was the regional settings, the london user had the setting to english(UK)
thus the date sent was in a different format from what was expected