HTTP 413 getStaticImage - Request entity too large
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 768
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
My application requires a static image with a ~10 geoJson overlays to put into a PDF report. After the 2nd geoJson circle, I get a HTTP 413 ("Request entity too large").
In the [Navigation service](https://docs.mapbox.com/api/navigation/) docs, Mapbox states
> If your account limits are larger than these defaults and you receive an HTTP 413 ("Request entity too large") or HTTP 414 ("Request URL too large") error when you make a GET request to either API, then using POST is a good option for you.
Is there a way to do a POST for static images as well?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the SDK's getStaticImage entry point and review how it builds requests for static images. Check the Mapbox static image API documentation and the existing request behavior for large GeoJSON overlays. Done means the SDK provides a supported way to submit these requests without the reported HTTP 413 failure, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100