404 on every call through BatchRequest
See original GitHub issueI get 404 (“Response status code does not indicate success: 404 (Not Found).”) on every call through BatchRequest
.
What I mean, before I used BatchRequest
and didn’t specify custom batchUri
:
var batch = new BatchRequest(service);
Since https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html I tried to use custom uri for each services. For eaxample for Youtube data API:
var batchRequest = new BatchRequest(service, "https://www.googleapis.com/batch/youtube/v3");
But on every call I heav got an error.
What I do incorrectly or it doesn’t work at all ?
Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:24 (15 by maintainers)
Top Results From Across the Web
Google API batch request returns HttpError 404 for every ...
It seems this problem is fixed with the newest version of the python library. However, if someone still has to solve it, or...
Read more >Weird error occurred when using BATCH request
I am currently facing an issue where am unable to execute any batch request from the Gateway hub system which is running on...
Read more >Receiving error 404 while fetching data through ...
Receiving error 404 while fetching data through batchGetReviews API ... an error : 404(Requested entity was not found) for some accounts when we...
Read more >api design - HTTP error 404 or 500 from an internal call to ...
If a call to API 2 within API 1 ends up with a 404 being returned (in my case because an object is...
Read more >Can't figure out why I am getting a 404 from open AI when ...
Can't figure out why I am getting a 404 from open AI when I make this call. Still a fairly new dev and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The API team has confirmed (with 100% certainty) that the fix is fully rolled out. I’ve been running my test code and @alenvall’s all morning and I haven’t seen any errors. I’ll leave this open until I hear from some of you, but this time this really should be working.
This is still being looked at by the API team. As soon as it is working I’ll update here.