[
https://issues.apache.org/jira/browse/NET-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved NET-638.
----------------------
Resolution: Fixed
Fix Version/s: 3.7
Thanks for the PR; applied:
URL: http://svn.apache.org/viewvc?rev=1800691&view=rev
Log:
NET-638 - Telnet subnegotiations hard-limited to 512 bytes - allow override
Modified:
commons/proper/net/trunk/src/changes/changes.xml
URL: http://svn.apache.org/viewvc?rev=1800694&view=rev
Log:
NET-638 - Telnet subnegotiations hard-limited to 512 bytes - allow override
Modified:
commons/proper/net/trunk/src/main/java/org/apache/commons/net/telnet/TelnetClient.java
commons/proper/net/trunk/src/main/java/org/apache/commons/net/telnet/TelnetInputStream.java
commons/proper/net/trunk/src/test/java/org/apache/commons/net/telnet/TelnetClientTest.java
> Telnet subnegotiations hard-limited to 512 bytes
> ------------------------------------------------
>
> Key: NET-638
> URL: https://issues.apache.org/jira/browse/NET-638
> Project: Commons Net
> Issue Type: Improvement
> Components: Telnet
> Affects Versions: 3.6
> Reporter: Daniel Leong
> Fix For: 3.7
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently using Commons.net's Telnet client for connecting to MUD/MUSH
> servers, and some servers use subnegotiation for sending out-of-band data
> with more than the hard-coded 512 bytes that TelnetInputStream limits it to.
> It looks like it would be straightforward to add an (optional) int
> constructor parameter to TelnetClient that passes it to a similar, new
> TelnetInputStream constructor parameter.
> I've got a workaround using a bunch of reflection, but it'd be nice to not
> need that.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
