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

Issue 748664 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Compat



Sign in to add a comment

Android Webview not rendering an external site (with User Agent modified)

Reported by rupesh.j...@gmail.com, Jul 25 2017

Issue description

Example URL:
https://login.etadirect.com/atni1.test/m

Steps to reproduce the problem:
Very Important: to reproduce, User Agent of the webview to be set to diff string than existing string. For example,
webviewSettings.setUserAgentString = "Vmware Browser version"
Login to this site: https://login.etadirect.com/atni1.test/m (external)
Username - e9901196
Password - gtt12345
The page does not loads properly rather "Network Instability Detected" is shown. 

What is the expected behavior?
The prob only exists with Webview and not on Chrome browser. 
1. To re-create the prob, create webview and modify the UA field to something else. In Vmware browser case, UA is appended with (Vmware Browser version). This causes the below url to load with "Network Instability Detected" error. 
2. If same webview is used without modifying the UA then the site works fine and shows proper page

What went wrong?
Modifying the UA field causing webview to show error which is not thrown from the server because we analyzed server response on both success case (UA not modified) and error case (UA modified)

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 5.0
Flash Version:
 
Components: Mobile>WebView
Cc: msrchandra@chromium.org nyerramilli@chromium.org sandeepkumars@chromium.org
Labels: Needs-Feedback
@rupesh.jain -- Thank You for the report.
Could you please upgrade to latest Stable, and let us know the behavior and if possible provide us the screen cast of the issue which would help us to triage the issue further.
Thanks in Advance.
It would also be good to see server-side logs, since you control that end, and logs from the device as well (bugreport / network requests captured by chrome://inspect?tracing - see: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/)
Cc: rbasuvula@chromium.org
@rupesh.jain : Could you please respond on comment #2 &3 and update the issue which would help us triage the issue further.

Thanks in Advance.

Comment 5 by cma...@chromium.org, Nov 17 2017

If this is no more an issue, let's mark it as won't fix it please.
Labels: -Needs-Feedback Needs-triage-Mobile WV-Triaged
Status: WontFix (was: Unconfirmed)
Marking the issue as Won't Fix due to lack of response from the user.
Please feel free to file a new bug if the issue is again seen.
Thank You.

Sign in to add a comment