Skip to content
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

Users can set "Host" header for fetch #11017

Closed
lucacasonato opened this issue Jun 17, 2021 · 4 comments · Fixed by #11020
Closed

Users can set "Host" header for fetch #11017

lucacasonato opened this issue Jun 17, 2021 · 4 comments · Fixed by #11020
Labels
bug Something isn't working correctly ext/fetch related to the ext/fetch

Comments

@lucacasonato
Copy link
Member

The host header should not be able to be set by the user. It should always be populated by reqwest / hyper.

@nayeemrmn
Copy link
Collaborator

Ref #6868.

@xdatcloud
Copy link

Hi there, I'm not familiar with background info about this issue, but it is possible to send request to endpoint behind Kubernetes Ingress with customized host header: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules .

@tlgimenes
Copy link

Guys, can we have a solution to passing host header? Any ideas on how to implement a transparent proxy with Deno's fetch?

@guifromrio
Copy link

We're being forced to use CF workers to proxy requests because of this limitation. Would be great for it to just work on deno.

bartlomieju pushed a commit that referenced this issue Jul 28, 2023
This adds an option to allow using the host header in a fetch call.
Closes #16840
Ref #11017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly ext/fetch related to the ext/fetch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants