[JIRA] Commented: (GRIZZLY-1679) Connection Abort on missing Content-Length header

  • From: "gerd.riesselmann (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Commented: (GRIZZLY-1679) Connection Abort on missing Content-Length header
  • Date: Thu, 15 May 2014 12:23:49 +0000 (UTC)
  • Auto-submitted: auto-generated


    [ 
https://java.net/jira/browse/GRIZZLY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=375434#action_375434
 ] 

gerd.riesselmann commented on GRIZZLY-1679:
-------------------------------------------

I can confirm it is fixed. Well done and thanks a lot for your efforts! 

> Connection Abort on missing Content-Length header
> -------------------------------------------------
>
>                 Key: GRIZZLY-1679
>                 URL: https://java.net/jira/browse/GRIZZLY-1679
>             Project: grizzly
>          Issue Type: Bug
>          Components: http-client
>    Affects Versions: 2.3.11
>            Reporter: gerd.riesselmann
>            Priority: Critical
>             Fix For: 2.3.12
>
>
> We at Strucr use the Grizzly HTTP Client to crawl a lot of sites, and we 
> again and again have problems where Grizzly incorrectly reports a 
> connection as having been remotely closed, that indeed was not.
> The behavior is triggered by a HTTP response that 
> - has no content-length, but 
> - also has Connection: Close
> Like this:
> HTTP/1.0 200 OK
> Date: Tue, 29 Apr 2014 22:18:06 GMT
> Server: Apache
> Cache-Control: no-cache
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Connection: close
> Content-Type: text/plain; charset=UTF-8
> The according request was sent as keep-alive:
> GET /robots.txt HTTP/1.1
> Host: www.aroundtheglobe.nl
> Connection: keep-alive
> The issue also occurs if the response is HTTP 1.1.
> Grizzyl in this case throws an java.io.IOException: Remotely Closed
> This is the stack trace:
> com.ning.http.client.providers.grizzly.GrizzlyAsyncHttpProvider$AsyncHttpClientTransportFilter$1.failed(GrizzlyAsyncHttpProvider.java:761),
> org.glassfish.grizzly.filterchain.DefaultFilterChain.notifyFailure(DefaultFilterChain.java:617),
> org.glassfish.grizzly.filterchain.DefaultFilterChain.throwChain(DefaultFilterChain.java:493),
> org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:165),
> org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:115),
> org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77),
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:550),
> org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112),
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:117),
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:56),
> org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:137),
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146),
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615),
> java.lang.Thread.run(Thread.java:701)
> The behavior is reproducible, and we also tested against but do not have 
> the problem with 
> - Netty,
> - Apache HTTP Client and 
> - Java URL 
> All major browsers work, too. 
> Since the Content-Length header is not required, but only SHOULD be send in 
> a response, we believe this is a bug of Grizzly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Commented: (GRIZZLY-1679) Connection Abort on missing Content-Length header

gerd.riesselmann (JIRA) 05/12/2014

<Possible follow-up(s)>

[JIRA] Commented: (GRIZZLY-1679) Connection Abort on missing Content-Length header

gerd.riesselmann (JIRA) 05/15/2014
Terms of Use; Privacy Policy; Copyright ©2013-2015 (revision 20150626.29986a4)
 
 
Close
loading
Please Confirm
Close