Response Compression

Nolxy compresses proxy responses at the gateway level using Brotli, gzip, or deflate — reducing bandwidth costs and improving client latency without any changes to your backend.

Encoding Negotiation

Nolxy reads the client's Accept-Encoding header and selects the best supported encoding using quality factor negotiation (RFC 7231). Brotli is preferred when available — it typically achieves 20–30% better compression than gzip for text payloads.

br (Brotli)

Best compression ratio for text. Quality level 4 (speed-optimized).

1st choice
gzip

Universal support. Level 6 by default.

2nd choice
deflate

Fallback for legacy clients.

3rd choice
identity

Returned when client explicitly requests no encoding.

No compression

When Compression Is Applied

Compression is skipped automatically when:

  • Response body is smaller than 1 KB (overhead exceeds savings)
  • Response body exceeds 50 MB (CPU protection)
  • Content-Type is not compressible (images, video, binary data)
  • Client does not send Accept-Encoding
  • Compressed output is larger than the original (rare, but possible)

Compressible Content Types

application/jsontext/htmltext/csstext/plainapplication/xmltext/xmlapplication/javascriptapplication/graphql+jsonimage/svg+xmlapplication/ld+json

Any text/* type or types with +json / +xml suffixes are also compressed automatically.

Response Headers

When compression is applied, Nolxy sets:

Content-Encoding: br
Vary: Accept-Encoding

Plan Requirements

Response Compression is available on Starter plans and above.

OpenAPI ImportWebSocket Proxying