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
With the release of boxo v0.10.1, the config for the Boxo Gateway handler config now has variable called DeserializedResponses.
When set to true, flat files (i.e. deserialized responses) are served, as all CAR and RAW files.
When set to false, flat files are not served, and the only CAR + RAW files served are those that can verify trustlessly (all CAR requests and RAW requests that have no path).
booster-http contains a significant amount of code aimed at partially replicating this behavior. However the Boxo code is more correct. Boost filters by file type, which serves some requests that cannot be verified trustlessly (RAW blocks served at a path are not verifiable)
We should switch booster-http to take advantage of the new parameter:
Remove --serve-files, --serve-blocks and --serve-cars parameters
Add parameter --serve-gateway=verifiable|all|none
verifiable: set DeserializedResponses to false
all: set DeserializedResponses to true
none: do not enable gateway handler
The text was updated successfully, but these errors were encountered:
dirkmc
changed the title
Use Deserializedr boxo parameters in booster-http
Use DeserializedResponses parameter for gateway in booster-http
Jun 20, 2023
Depends on #1492
With the release of boxo v0.10.1, the config for the Boxo Gateway handler config now has variable called
DeserializedResponses
.When set to
true
, flat files (i.e. deserialized responses) are served, as all CAR and RAW files.When set to
false
, flat files are not served, and the only CAR + RAW files served are those that can verify trustlessly (all CAR requests and RAW requests that have no path).booster-http contains a significant amount of code aimed at partially replicating this behavior. However the Boxo code is more correct. Boost filters by file type, which serves some requests that cannot be verified trustlessly (RAW blocks served at a path are not verifiable)
We should switch booster-http to take advantage of the new parameter:
--serve-files
,--serve-blocks
and--serve-cars
parameters--serve-gateway=verifiable|all|none
verifiable
: setDeserializedResponses
tofalse
all
: setDeserializedResponses
totrue
none
: do not enable gateway handlerThe text was updated successfully, but these errors were encountered: