BadCode | 恶意代码逃逸源代码 http://payloadsonline

This code helps me

Your code is vulnerable to local file inclusion (LFI). A potential attacker can traverse your file system and include something like:

exit means exit php ... for your test and also for phpunit.

your may use exeptions to handle exit points. otherwise no mock will go on.

I'm not really certain of what you mean by "2nd" loop. For clarity I will refer to the loops as inner and outer.

continue is used to essentially skip to the next iteration of the loop in which continue is inside of. Therefore, if you have a nested loop, placing continue inside the inner loop, will skip to the next iteration of itself. continue won't have any effect on the outer loop if inside of the inner loop.

If this is not what's happening, then either something is wrong with Java, or something is wrong with your logic somewhere. I doubt that something is wrong with Java.

Try using your debugger to figure out what the values are of variables associated with your conditional. Your debugger can help you better than we can.

There are two problems with your code

1. Arrays.asList(badcodes) returns a List, while code is a WebElement: you're comparing two different types, so check will never be true
2. You say that code is more than three characters, but List.contains expects equality.

You might be confusing String.contains and List.contains.

myString.contains(code) will return true if code is a substring of the String myString myList.contains(code) will return true if code is an element of the List myList

In your code, Arrays.asList(badcodes).contains(code) calls List.contains, and returns false because - as you say - code is longer than any of the Strings you're comparing to.

How do you fix it?

1. Convert code to a String. You should know how to do that, because you already do it in the System.out.println above.
2. Ensure code has the same length as the strings you're comparing to. You should know how to do that, because you already do it in the System.out.println above.

Your first option would not do what you expect to do. And even if someArray.equals(anotherArray) would do an element-wise comparison (which it doesn't) - you would need to have the special array contain all objects of the existing array, in the exact same order. In that sense: first understand why this approach is flawed in many ways, to then drop it.

The second option is fine, but if you really want to "improve" the whole thing - use ArrayList instead - which has a contains() method.