[
https://issues.apache.org/jira/browse/AVRO-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547055#comment-13547055
]
Brock Noland commented on AVRO-1226:
------------------------------------
I am no expert in the AVRO IPC protocol so I maybe speaking out of turn here.
However, what if we changed the IPC protocol so that the first item exchanged
between two avro processes was a magic cookie. This way, if a port
scanner/monitor connected to an avro service and sent it bad data, we could
identify this and throw and error like "Client is not speaking avro".
This would be an incompatible change.
> Non-Avro data causes runtime exceptions/errors when sent to Avro IPC port
> -------------------------------------------------------------------------
>
> Key: AVRO-1226
> URL: https://issues.apache.org/jira/browse/AVRO-1226
> Project: Avro
> Issue Type: Improvement
> Affects Versions: 1.7.3
> Reporter: Brock Noland
>
> AVRO-1111 put in a stop gap measure to stop Avro from throwing an OOMError
> when something like an HTTP request was sent to an AVRO IPC port. The general
> issue of port scanning/monitoring causing Avro to throw opaque runtime errors
> still exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
