Gateway requests responds with `403 - Forbidden`
See original GitHub issueWhen in the Download
page, the user shouldn’t have to have an IPFS instance or daemon running, so we’ll use the ipfs.io
gateway to fetch the files and download them.
The problem here is that when making the request the response is always 403 - Forbidden
.
https://github.com/ipfs-shipyard/ipfs-share-files/blob/7ed1070796187f0079620e7b836f31b8e23c4dbb/src/pages/download/Download.js#L20
Both in Postman or directly in the browser the response comes OK, but not in the app.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Fix 403 Forbidden errors when connecting to API Gateway ...
The HTTP 403 Forbidden error most commonly occurs when private DNS is enabled for an API Gateway interface VPC endpoint that's associated ...
Read more >What Is the 403 Forbidden Error and How to Fix It (8 Methods ...
403 Forbidden error message means that the server is unable to authorize a particular request made by a user. What Causes 403 Forbidden?...
Read more >403 Forbidden Error: What It Is and How to Fix It - Airbrake Blog
The 403 Forbidden Error is an HTTP response status code that indicates an identified client does not have proper authorization to access the...
Read more >Resolve Amazon API Gateway HTTP 403 Forbidden error
The HTTP 403 Forbidden error indicates the client is forbidden from accessing a valid URL. Although the server seems to have understood the ......
Read more >getting message: forbidden reply from AWS API gateway
I might be too late but one of the reasons API Gateway would give "forbidden" message is when you pass data in request...
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
Huge thanks to @lidel and @lgierth, this is now fixed!
Wow, thanks @lidel! It really is strange!
@lgierth can you please ping here when it is fixed?