actually just: res.send(idbanks_csv) would avoid the red ink and still work mm something is still broke let me recrete locally

thanks for your help Tom

Ahh! "Missing required request header. Must specify one of: origin,x-requested-with" from the serverless environment on the zip fetch. Serverless cells do not have origin headers (no CORS) so its breaking early did you perhaps add security to the proxy later. If you need a CORS proxy you can also use fetchp

thank you Tom. I am now trying with both fetch and fetchp, but i am still stucked...

so am I. Its tough. I have to eat dinner now. I have had some succcess by adding '{"headers":{"origin":"observablehq.com"}}}' to the fetch request. fetchp still fails for other reasons but maybe the other proxies work with that extra setting super simplest solution is to jsut host that zip file elsewhere, as there is some complex access logic on it also you are not exposing your errors on the original fetch, so its very hard to debug. you ideally need to pipe all your errors out into the repsonse

Thanks Tom, there is no hurry. I can deposit the csv on a public server, but the point and the interest with your technique is to keep it in sync with the initial provider's url, whose content is updated monthly. The deployment was working fine 2 weeks ago, something has changed somewhere

I did it! But it was kinda subtle.

Great !

hi I don't think you have merged the fixed verion:https://observablehq.com/@tomlarkworthy/stockage-cdn-proxy-du-fichier-de-reference-insee-bdm-idbank yet. I want to delete it soon