New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 840187 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

CronetHttpURLConnection.getResponse() hangs when server does not reply to any data after connection is established

Reported by danny192...@gmail.com, May 6 2018

Issue description

Example URL:

Steps to reproduce the problem:
1. Create a CronetHttpURLConnection and connect
2. Call getResponseCode()
3. Server does not reply to any data after connection is established

What is the expected behavior?

What went wrong?
When server does not reply to any data after connection is established, CronetHttpURLConnection.getResponse() hangs.

The read timeout I set does not take effect here, and i think there is a need for a timeout similar to TTFB(Time To First Byte).

Did this work before? N/A 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: 
Flash Version:
 
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: Needs-Feedback Triaged-Mobile
@danny19211949: Could you please update Chrome to latest version #66.0.3359.126 and check if you still face the issue? If so attach a sample file where you're seeing this issue and OS, details of your device for triaging of the issue?

Thanks!!
Components: -Internals>Network Internals>Network>Library
Labels: -Needs-triage-Mobile -Triaged-Mobile
danny19211949: can you get attach a NetLog?  It will give us more information on the interaction between cronet and your test server.

The setReadTimeout should be respected. There is a unit test for it:
https://cs.chromium.org/chromium/src/components/cronet/android/test/javatests/src/org/chromium/net/urlconnection/CronetHttpURLConnectionTest.java?rcl=978e75074076c6997f0eca4c9fa77c9b9f999a6b&l=134
Ping @reporter, we won't be able to proceed on this bug without answers to the above.
@danny19211949: According to the documentation for setReadTimeout():
https://developer.android.com/reference/java/net/URLConnection.html#setReadTimeout(int)
This method can be used for setting a timeout "when reading from Input stream", but getResponseCode() is somewhat orthogonal to the InputStream so the timeout may not apply.

Comment 6 by mmenke@chromium.org, May 29 2018

Status: Archived (was: Unconfirmed)
Archiving issue due to lack of followup.  Think this may be expected behavior.

Sign in to add a comment