New issue
Advanced search Search tips

Issue 879156 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Aug 30
Cc:
mmenke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

unable to access cached site

Reported by ksumes...@gmail.com, Aug 30 
Example URL:
www.google.com

Steps to reproduce the problem:
1. go to www.google.com
2. perform a search for google (This is ensure that there is some browser history present).
3. after search is completed perform a search for cache:google.com (you can use any site in place of google.com ex:cache:facebook.com)

What is the expected behavior?
browser navigate to google cache for the site

What went wrong?
browser displays you are offline message.

Did this work before? N/A 

Chrome version: 68.0.3440.91  Channel: stable
OS Version: 8.1.0
Flash Version: 

This issue occurs only if we have some history of google search in the memory. if we clear browser data and perform search for cache:google.com then this bug does not occurs.
chrome-net-export-log.json
629 KB View Download
Screenshot_20180830-193834.png
113 KB View Download

Comment 1 by zhongyi@chromium.org, Aug 30

Cc: mmenke@chromium.org
The request for "cache:google.com" was able to be sent and received a response from the server via a QUIC session. However the request was then cancelled by upper layer. It may be the MojoAsyncResourceHandler cancelling the request? 

t=8015 [st=145]     +URL_REQUEST_DELEGATE  [dt=4]
t=8015 [st=145]        DELEGATE_INFO  [dt=4]
                       --> delegate_blocked_by = "MojoAsyncResourceHandler"
t=8019 [st=149]     -URL_REQUEST_DELEGATE
t=8019 [st=149]      CANCELLED
t=8019 [st=149]   -URL_REQUEST_START_JOB
                   --> net_error = -3 (ERR_ABORTED)

Comment 2 by mmenke@chromium.org, Aug 30

Components: Blink>ServiceWorker
The "MojoAsyncResourceHandler" cancelling the request means the renderer canceled it.  It's also possible it was cancelled through some sidechannel.

I'm adding the ServiceWorker component, as it appears the network request was made by a service worker.  I'm not sure that this is a Chrome bug - may be an issue with Google's mobile search page or something.  It is really easy to reproduce this, even on desktop (With devtools simulating a phone), which should hopefully make investigating not too bad.

Comment 3 by kinuko@chromium.org, Aug 30 

Guess the same issue as issue 878450?

Comment 4 by kinuko@chromium.org, Aug 30

Mergedinto: 878450
Status: Duplicate (was: Unconfirmed)
I suppose so, closing this as a duplicate, please reopen otherwise.
►

Sign in to add a comment