[
https://issues.apache.org/jira/browse/AVRO-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803914#action_12803914
]
Scott Carey commented on AVRO-340:
----------------------------------
I believe, but could be wrong, that both chunked transfer encoding and standard
Content-Length transfer encoding is required (client side) to be HTTP 1.1
compliant, but a server can do whatever it wants.
This is all typically handled at the HTTP library level.
I have seen test HTTP server programs that can purposely send flawed transfer
encoding to a client. Its easy to crash IE or Safari this way -- or at least
was a couple years ago.
It may be useful to have a "evil server" and "evil client" tool to make sure
implementations are robust. The same is true for any transport layer, and is
one of the reasons why building your own TCP based transport is not as easy as
it seems. You don't want someone to telnet to a port and take down your server.
> specify http transport in spec
> ------------------------------
>
> Key: AVRO-340
> URL: https://issues.apache.org/jira/browse/AVRO-340
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.3.0
>
>
> The use of HTTP as an Avro RPC transport should be described in the Avro spec.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
