[JBoss JIRA] Commented: (NETTY-369) Invalid version format when reading HTTP response
Trustin Lee (JIRA)
jira-events at lists.jboss.org
Wed Jan 12 05:27:49 EST 2011
[ https://issues.jboss.org/browse/NETTY-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574891#comment-12574891 ]
Trustin Lee commented on NETTY-369:
-----------------------------------
Could you please post the HTTP response itself instead of a URL so that I can figure out what is wrong?
> Invalid version format when reading HTTP response
> -------------------------------------------------
>
> Key: NETTY-369
> URL: https://issues.jboss.org/browse/NETTY-369
> Project: Netty
> Issue Type: Bug
> Components: Handler
> Affects Versions: 3.2.3.Final
> Environment: Mac OS X 10.6, Java 6
> Reporter: Matt Revelle
> Assignee: Trustin Lee
>
> When reading an HTTP response from a server that does not include any headers, the version of the HTTP protocol is attempted to be parsed from the HTTP body and results in an IllegalArgumentException being thrown.
> For example, there is a page served by the popular Tumblr blogging platform which does not include any HTTP headers in its response:
> http://remiel.info/post/1601242301/making-the-leap-to-ssd-on-a-macbook
> The accompanying stack trace is:
> java.lang.IllegalArgumentException: invalid version format: <!DOCTYPE
> at org.jboss.netty.handler.codec.http.HttpVersion.<init>(HttpVersion.java:108)
> at org.jboss.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:68)
> at org.jboss.netty.handler.codec.http.HttpResponseDecoder.createMessage(HttpResponseDecoder.java:110)
> at org.jboss.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:198)
> at org.jboss.netty.handler.codec.http.HttpClientCodec$Decoder.decode(HttpClientCodec.java:113)
> at org.jboss.netty.handler.codec.http.HttpClientCodec$Decoder.decode(HttpClientCodec.java:101)
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:471)
> at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:444)
> at org.jboss.netty.handler.codec.http.HttpClientCodec.handleUpstream(HttpClientCodec.java:77)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:350)
> at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
> at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the netty-dev
mailing list