3 ms·
Question: deno run https://deno.land/std/examples/welcome.ts This works - it downloads the code from that URL, then compiles and runs it. But if you visi
by simonw 7y ago
Question:
deno run https://deno.land/std/examples/welcome.ts
This works - it downloads the code from that URL, then compiles and runs it.
But if you visit https://deno.land/std/examples/welcome.ts https://deno.land/std/examples/welcome.ts in your browser you get back HTML, not raw code.
Anyone know how this works? Is deno.land a special case or is there some Accept header cleverness or something going on?
- simonw 7y agoFigured this out myself: $ curl 'https://deno.land/std/examples/welcome.ts' console.log("Welcome to Deno "); So this is an Accept header trick. If I do this instead: $ curl 'https://deno.land/std/examples/welcome.ts' -H 'Accept: text/html' I get back the full HTML version of the page.
- akamaozu 7y agoWas waiting for the first person to point out that what you get when you visit a url is not guaranteed to be the exact same on a subsequent visit. Not seeing how url-based package management is safer when a package host can use a server that sends a special payload to certain requester ips, headers, cookies or referrer. Until there are firm guarantees around what you get from a url, a trust-able third party is needed, even if just as an option.