-
Notifications
You must be signed in to change notification settings - Fork 11
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
Support IPv6 #40
Comments
This is a long-standing need for Heroku and something we've been wanting for a long time! |
Among other things IPV6 is needed in the system to token authenticate with some CDN vendors. If my viewers have an ipv4 address I see it, and token authenticate URLs for them using it. The CDN sees their IPV6 address and 403's the response. Perhaps a first step is for the routers to pass through IPV6 info as a header?? The only alternative for me is to put a CDN infront of heroku and migrate all my CNAME domains off the heroku router. |
Thanks for the feedback! We're in the process of planning our roadmap now and IPv6 is on our radar and up prioritization for our networking team. We've also had that exact conversation about what first steps we can provide in a shorter timeframe to get IPv6 support at the edge/router first. I'll update here when our networking team has scoped this out in a bit more detail. |
We are being asked if our systems support IPv6 by some of our customers, and right now I have to answer this as no due to Heroku. Since it's been about five months - any update on this? I also don't see this one on https://github.com/orgs/heroku/projects/130/views/1 - does that mean it's not currently being investigated? |
I requested the following to Heroku in december last year.
Their response at the time (though I'm not sure if my request went beyond the support team) was the following:
|
I have a client that would really appreciate some movement on this. |
The time is ticking as the US Government is transitioning to IPv6-only networking over the next two years (see https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). This will force a real exodus from Heroku of all its vendors and contractors if this issue is not prioritized ASAP. It's already happening! |
This wasn't flagged here, but:
Good to see :) |
Does Expedited WAF helps for this case? |
Short: The industry is moving from IPv4 and IPv6 is the future. Here's some more context heroku/roadmap#40. Internal Heroku link for more context: https://salesforce-internal.slack.com/archives/C06NM9FFY57/p1732035124610499?thread_ts=1731970807.940289&cid=C06NM9FFY57
Short: The industry is moving from IPv4 and IPv6 is the future. Here's some more context heroku/roadmap#40. Internal Heroku link for more context: https://salesforce-internal.slack.com/archives/C06NM9FFY57/p1732035124610499?thread_ts=1731970807.940289&cid=C06NM9FFY57
IPv6 is the future. Here's some more context heroku/roadmap#40. Related heroku/ruby-getting-started#165
* Change default process type host to IPv6 `::` IPv6 is the future. Here's some more context heroku/roadmap#40. Related heroku/ruby-getting-started#165 * Update gems * Use puma to support IPv6 and IPv4 in local tests * Changelog
Required Terms
What service(s) is this request for?
DNS, routing, dynos, logging
Tell us about what you're trying to solve. What challenges are you facing?
Please add support for IPv6 for hostnames served on Heroku. IPv6 is the current version
of the IP protocol, and on many networks is faster than the legacy IPv4.
The text was updated successfully, but these errors were encountered: