Norman Maurer 9707eba2b3 [#2428] Proper fix of incorrect port range check ... Motivation: In the Internet Protocol, the valid port number range is from 1 to 65535 (inclusive on the both side.) However, SocksCmdRequest and SocksCmdResponse refuses to construct itself when the port number 65535 is specified. Beside this it excepts 0 as port number which should not allowed. Modification: * Not raise an exception when the specified port number is 65535. * Raise an exception when the specified port number is 0 Result: Fixes #2428		2014-04-30 08:19:13 +02:00
..
SocksAuthRequestDecoderTest.java	Change the return type of EmbeddedChannel.read*() from Object to an ad-hoc type parameter	2013-12-16 22:22:47 +09:00
SocksAuthRequestTest.java	[#787] Move the socks package to the right place	2012-12-04 09:14:05 +01:00
SocksAuthResponseDecoderTest.java	Change the return type of EmbeddedChannel.read*() from Object to an ad-hoc type parameter	2013-12-16 22:22:47 +09:00
SocksAuthResponseTest.java	[#2428] Proper fix of incorrect port range check	2014-04-30 08:19:13 +02:00
SocksCmdRequestDecoderTest.java	[#2428] Proper fix of incorrect port range check	2014-04-30 08:19:13 +02:00
SocksCmdRequestTest.java	[#2428] Proper fix of incorrect port range check	2014-04-30 08:19:13 +02:00
SocksCmdResponseDecoderTest.java	Fix an inspector warning	2014-02-06 15:03:03 -08:00
SocksCmdResponseTest.java	[#2428] Proper fix of incorrect port range check	2014-04-30 08:19:13 +02:00
SocksCommonTestUtils.java	Revamp the core API to reduce memory footprint and consumption	2013-06-10 16:10:39 +09:00
SocksInitRequestTest.java	enable checkstyle for test source directory and fix checkstyle errors	2013-03-30 13:18:57 +01:00
SocksInitResponseTest.java	[#787] Move the socks package to the right place	2012-12-04 09:14:05 +01:00