-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 ClientError is misleading when export is too large #906
Labels
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
yoshi-automation
added
triage me
I really want to be triaged.
🚨
This issue needs some love.
labels
Sep 9, 2020
dazuma
added
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
and removed
🚨
This issue needs some love.
triage me
I really want to be triaged.
labels
Sep 14, 2020
I have a workaround that requires one extra call to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
My team is using the client to download files. A line like:
Is raising a
Google::Apis::ClientError
with ane.inspect
like:This threw us for a real loop, because most of these requests work just fine, it was just an occasional file that consistently got a 403. We finally tested the specific file in https://developers.google.com/drive/api/v3/reference/files/export and found that the full response from the API is:
Describe the solution you'd like
It would be great to get that JSON object back in the ClientError's
body
field, or some other mechanism.Describe alternatives you've considered
Right now, we're just having to assume that a 403 from this endpoint means that the file is too large. But that's not great, since https://developers.google.com/drive/api/v3/handle-errors lists a whole bunch of reasons that we might be getting a 403.
The text was updated successfully, but these errors were encountered: