You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Daniel Leong (JIRA)" <ji...@apache.org> on 2017/07/01 13:41:00 UTC

[jira] [Commented] (NET-638) Telnet subnegotiations hard-limited to 512 bytes

    [ https://issues.apache.org/jira/browse/NET-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071228#comment-16071228 ] 

Daniel Leong commented on NET-638:
----------------------------------

Created a PR on the Github project: https://github.com/apache/commons-net/pull/26

> 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
>   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)