-
Notifications
You must be signed in to change notification settings - Fork 1
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
BACKHOST does not work properly #1
Comments
Hello! I've been following that issue too, and saw the backlink to this issue a while ago so I thought I'd chime in! Deno recently (as of v1.36) merged a way to send Host headers via the const client = Deno.createHttpClient({
allowHost: true,
});
const res = await fetch("http://localhost:4545/echo_server", {
headers: {
"host": "example.com",
},
client,
}); (Note that you need to run deno with |
@LucienLeMagicien Many thanks for chiming in! I was almost starting to look to port adobe/fetch to Deno... Work relieved! |
My pleasure! It seems you're not aware of this either (since you were looking at reimplementing a module), so just so you know: Deno can now also use npm modules directly, and the "Node.js compatibility layer" is pretty good (and they track compatibility issues in their issues). Since v1.28 (https://deno.com/blog/v1.28) you can do things like (The Host header also didn't work when doing this at first, but they fixed it (in v1.34) after I opened an issue 👌) |
@LucienLeMagicien I was seeking to re-implement because I wanted it to be either runtime-native or runtime-agnostic. |
Thanks to denoland/deno#11017, Deno effectively disabled all domain fronting attempts. Apparently Deno's coreteam considers server-side code as users. A modified fetch implementation might be required to bypass this restriction.
Cloudflare Workers also disabled domain fronting via workers.
The text was updated successfully, but these errors were encountered: