Page MenuHomePhabricator

If the Conduit server asserts it has the "gzip" capability, compress requests
ClosedPublic

Authored by epriestley on Apr 14 2020, 11:45 PM.
Tags
None
Referenced Files
F15461003: D21119.id50298.diff
Tue, Apr 1, 4:14 AM
F15458648: D21119.id50298.diff
Mon, Mar 31, 5:54 AM
F15442839: D21119.id50298.diff
Thu, Mar 27, 12:48 AM
F15441430: D21119.id50296.diff
Wed, Mar 26, 6:11 PM
F15436091: D21119.id.diff
Tue, Mar 25, 11:54 AM
F15429872: D21119.diff
Mon, Mar 24, 4:43 AM
F15424957: D21119.id50296.diff
Sun, Mar 23, 1:20 AM
F15421782: D21119.id50296.diff
Sat, Mar 22, 2:10 AM
Subscribers
None

Details

Summary

Ref T13507. For various messy reasons we can't blindly assume the server supports "gzip" -- but if the server tells us it does, we're on firmer ground.

If the server returns an "X-Conduit-Capabilities: gzip" header and we have compression support locally, compress subsequent requests.

This restores D21073, which was reverted by D21076.

Test Plan

With a gzip-asserting server, added debugging code and ran various "arc" commands. Saw the 2nd..Nth calls hit compression code.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable