blocked with this issue not able to download the documents from  google drive.  even tried open the document and tried to download the same issue still exists.

Networking triager on duty.

I cannot reproduce it with Chrome 69.0.3497.100 on Mac OS X. 
Could you try to remove all extensions and reproduce the issue?

If reproducible, please capture the network log by following instructions at chrome://net-export/ while reproducing the issue, and share it with me or attach here.

[vennysuya.tnvl]:  Could you please response to comment 3?  IF you don't respond, we have no path forward here, and will have to close the issue.

 I am using Version 69.0.3497.100 (Official Build) (32-bit) windows machine
 i had one extension called citrix. removed the same. 
still the issue exists.(19/10/2018)please find the network log as expected.

Deleted: chrome-net-export-log.json 16.6 MB

chrome-net-export-log.json 16.6 MB Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

to add on the comment 5 , the issue exists with the download  . not specific to right click.
and the 403 exception occurred for  pdf ,jpg and txt files also .. 
please find the attached log file for this .

Deleted: chrome-net-export-log-2.json 6.4 MB

chrome-net-export-log-2.json 6.4 MB View Download

Thanks for the logs! 

In the log from Comment 7 I see 403 returned in QUIC session to doc-0g-6g-docs.googleusercontent.com:

t=151788 [st= 2099]    QUIC_CHROMIUM_CLIENT_STREAM_READ_RESPONSE_HEADERS
                       --> :status: 403
                           access-control-allow-credentials: false

I'm not sure why would does it happen, and leaving it to current triager on duty. 

Oh, one observation. This QUIC session only has 2 requests. 
First gets 302, and the second gets 403.

[vennysuya.tnvl]: could you retry after disabling QUIC and see if the issue repros? You can disable QUIC by visiting chrome://flags/#enable-quic, and then change default to disabled.

It looks more like a server issue rather than a QUIC issue to me. The original request was requesting resource under url_1: , which created a QUIC session and sent the request after successful handshake. A response was received in that session to redirect to url_2. A request was then sent via a different QUIC session to docs.google.com to request url_2. A new response was received in the second QUIC session to redirect to url_3. A third request was sent on the first QUIC session (since that's the same host) to request url_3, which eventually got a 403. 

url_1: https://doc-0g-6g-docs.googleusercontent.com/docs/securesc/1a5ue8qi517n6ln5l2vvvd91q7rs3f31/1tmsajb27582ktsvn0oajrtmgio1osoi/1539936000000/01595539222359278587/01595539222359278587/1lHPzTRacV8kFODl-Mbk7CTY8rz9CAoIP?e=download

url_2: https://docs.google.com/nonceSigner?nonce=fu294fbli2bh4&continue=https://doc-0g-6g-docs.googleusercontent.com/docs/securesc/1a5ue8qi517n6ln5l2vvvd91q7rs3f31/1tmsajb27582ktsvn0oajrtmgio1osoi/1539936000000/01595539222359278587/01595539222359278587/1lHPzTRacV8kFODl-Mbk7CTY8rz9CAoIP?e%3Ddownload&hash=u8s4ir96jv2mub5hqo7tm1ie9au8s43d

url_3: https://doc-0g-6g-docs.googleusercontent.com/docs/securesc/1a5ue8qi517n6ln5l2vvvd91q7rs3f31/1tmsajb27582ktsvn0oajrtmgio1osoi/1539936000000/01595539222359278587/01595539222359278587/1lHPzTRacV8kFODl-Mbk7CTY8rz9CAoIP?e=download&nonce=fu294fbli2bh4&user=07879164006196055451&hash=vdppep5i44ck4visg0irfv4pmn1en6hq

Friendly ping. Could you try with QUIC disabled as in comment #10? Thanks!

Reporter: please retry with QUIC disabled, see comment #10.

I will try and get back to you .

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Dear all,

 I didn't disable the QUIC . but rather by default my chrome version has been updated .NOw  I can able to download the documents from drive.
 Chrome version :Version 70.0.3538.110 (Official Build) (32-bit)

 And the issue has been resolved .
 

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Seems no longer reproducible

Yes after the update of chrome it's not reproducible.

On Wed, Nov 21, 2018, 8:42 PM morlov… via monorail <
monorail+v2.2514459053@chromium.org wrote: