feat: Document support for brotli compression#2750
Merged
Conversation
- apify/apify-core#28971 added support for brotli compression to BE. - Key value store endpoints didn't support it recently. I guess this was a bug in doc, but it's all good now :-) - Dataset items endpoints support it as well now. - I put brotli at the beginning of the lists, it should be the first choice whenever possible.
Contributor
|
🗑️ Preview for this PR was deleted. |
Contributor
|
Important Action required — @mixalturek please coordinate this docs PR with the Python API client PR linked below. Because this PR modifies the OpenAPI specification, the generated models in A companion PR has been opened in
|
This was referenced Jul 8, 2026
fnesveda
approved these changes
Jul 9, 2026
nmanerikar
approved these changes
Jul 9, 2026
nmanerikar
left a comment
nmanerikar
left a comment
Contributor
There was a problem hiding this comment.
I think it might be apt to have one person from the Technical Writers' team on apify-docs reviews
cc: @szaganek
mixalturek
added a commit
to apify/apify-client-js
that referenced
this pull request
Jul 9, 2026
- apify/apify-core#28971 added support for brotli compression to BE. - Pros: higher compression, cons: more CPU intensive. - The code could be running on too old Node.js, so brotli compression is applied only if possible; the code otherwise falls back to gzip. Too small payloads and unsupported types are still not compressed - no change. ### Related PRs - apify/apify-core#28971 - apify/apify-docs#2750 - #962 - apify/apify-client-python#927 - apify/apify-sdk-python#1031
mixalturek
pushed a commit
to apify/apify-client-python
that referenced
this pull request
Jul 9, 2026
> [!IMPORTANT] > **Replace this PR title and description before merging.** > - Title: a Conventional Commits message describing the actual model changes (e.g. `chore: ...` for a routine sync, or `refactor:`/`feat:`/`fix:` when models meaningfully change). > - Description: summarize what changed in the models. - Updates the auto-generated Pydantic models and TypedDicts based on the proposed OpenAPI specification changes. - Based on apify-docs PR [#2750](apify/apify-docs#2750).
Contributor
Author
It's good enough, merging ;-) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related PRs