#3881 closed enhancement (fixed)

Make CBOR usage in HTTP Storage Protocol tied to HTTP headers

Reported by: itamarst Owned by: GitHub <noreply@…>
Priority: normal Milestone: HTTP Storage Protocol
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

  1. We might want to support JSON too.
  2. We should be respecting HTTP headers.

So:

  • Client must set encoding header when sending CBOR.
  • Client must set Accept header so it can receive CBOR.
  • Server must check for the Accept header when responding in CBOR.
  • Server must set encoding header when sending CBOR.
  • Refactor code so anything CBOR-specific is centralized, rather than scattered throughout the server/client implementations.

Change History (1)

comment:1 Changed at 2022-03-18T14:36:33Z by GitHub <noreply@…>

  • Owner set to GitHub <noreply@…>
  • Resolution set to fixed
  • Status changed from new to closed

In c632aa1/trunk:

Merge pull request #1185 from tahoe-lafs/3881-cbor-refactor

CBOR refactor for HTTP storage protocol

Fixes ticket:3881

Note: See TracTickets for help on using tickets.