-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: gateway-conformance support for query parameter #35
Comments
it looks like the incoming accept header is overriding things:
From a browser request, this is automatically being set for me:
for a fetch request from the browser, this is also being set for me: var resp = await fetch("http://helia-http-gateway.localhost/ipfs/bafkreialihlqnf5uwo4byh4n3cmwlntwqzxxs2fg5vanqdi3d7tb2l5xkm?format=dag-json")
var resp = await fetch("http://helia-http-gateway.localhost/ipfs/bafkreialihlqnf5uwo4byh4n3cmwlntwqzxxs2fg5vanqdi3d7tb2l5xkm?format=dag-json", {headers: {}})
// both result in: helia:verified-fetch incoming accept header "*/*" curl also results in |
if I try I get
|
i'm doing some tests on ipfs/helia-http-gateway#67 and noticed one oddity. we're not converting dag-json properly? the content-type is being set, incorrectly, to
text/plain; charset=utf-8
We should be falling into the block similar to
helia-verified-fetch/packages/verified-fetch/src/verified-fetch.ts
Lines 243 to 249 in 39bb14e
raw
todag-json
?requesting http://helia-http-gateway.localhost/ipfs/bafkreialihlqnf5uwo4byh4n3cmwlntwqzxxs2fg5vanqdi3d7tb2l5xkm?format=dag-json results in the following output from verified-fetch:
gateway conformance output is:
The text was updated successfully, but these errors were encountered: