You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have to override Connection and Accept-Encoding in order to for a request to work. Need to investigate why these overrides are needed, and find solutions to remove headers override from notarization flow. The request theoretically should work with just headers from user browser history.
Edit 1: overriding request header with accept-encoding: identity is expected behavior
The text was updated successfully, but these errors were encountered:
@0xtsukino, the prover uses accept-encoding: identity to tell the server not to use http compression (like gzip) for the response.
If the server sent a compressed response, the parties would have to decompress it in MPC which would be prohibitively expensive.
Thanks @themighty1 - that makes sense, so accept-encoding: identity is expected behavior.
0xtsukino
changed the title
Remove connection: close; accept-encoding: identity headers override
Remove connection: close headers override
Nov 25, 2023
Currently we have to override
Connection
andAccept-Encoding
in order to for a request to work. Need to investigate why these overrides are needed, and find solutions to remove headers override from notarization flow. The request theoretically should work with just headers from user browser history.Edit 1: overriding request header with
accept-encoding: identity
is expected behaviorThe text was updated successfully, but these errors were encountered: