--authorization=basic breaks gzipped request decompression

[nevumx]

Short description

Issue exists on OPA v0.65.0 and EOPA v1.22.0, although they have different error messages for some reason... 😕

If the --authorization=basic flag is passed to an opa run -s cli command, opa will output an error on receiving a properly gzipped HTTP request with the Content-Encoding: gzip header.

Steps To Reproduce

1. Run an opa server with the --authorization=basic flag, e.g. opa run -s --authorization=basic.
2. Execute a gzipped curl request on another shell window, like echo -n '{}' | gzip | curl -H "Content-Encoding: gzip" --data-binary @- http://127.0.0.1:8181/v1/data
3. Observe the error given:

{
  "code": "invalid_parameter",
  "message": "invalid character '\\x1f' looking for beginning of value"
}

Or with EOPA:

{
  "code": "invalid_parameter",
  "message": "yaml: control characters are not allowed"
}

Expected behavior

In this case, some error about there being no input or path after /v1/data, but with more policies/proper input, there should be no errors; the request should decompress as expected, and the evaluation/response should continue as expected.

[philipaconrad]

Ah yep! This looks like a case where the server/authorizer package isn't handling gzipped request bodies correctly. I'll see if there's a straightforward fix for this.