search

heroku / roadmap

This is the public roadmap for Salesforce Heroku services.
13 stars 0 forks source link

Support IPv6 #40

Open rajiv opened 2 years ago

rajiv commented 2 years ago

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.

danaspiegel commented 2 years ago

This is a long-standing need for Heroku and something we've been wanting for a long time!

davidlowry commented 1 year ago

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.

elimchaysengSF commented 1 year ago

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.

karlbecker commented 1 year ago

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?

christiaanwesterbeek commented 1 year ago

I requested the following to Heroku in december last year.

There is a Dutch requirement/policy in place that all government websites and semi-government websites must support ipv6. https://www.digitaleoverheid.nl/nieuws/overheden-stap-nu-over-naar-ipv6/

Heroku does not support ipv6, but is used by dozens of such sites, including [...]. We are now making an effort to move away from Heroku for this ipv6 reason only. I now have sites running as a test on nodechef and AWS Lightsail. They pass the ipv6 test but score worse on other security items compared to Heroku.

If you can deliver on ipv6 support soon, you can prevent dozens of sites to be migrated away, enjoy the other security items, and make us happy with the ease of deployment. The latter has become even more obvious when we have been trying to deploy on other platforms.

To summarize; can you and/or when will you support ipv6?

Their response at the time (though I'm not sure if my request went beyond the support team) was the following:

I totally acknowledge your concern about this. Heroku doesn't support IPv6 currently but supporting this is definitely on our radar, but it's not currently the top priority.

We appreciate your feedback and will note this for our engineering team to consider. We don't have an ETA for when this may be implemented (or if it will be). Please watch our changelog and blog for any updates.

Let us know if you have any other questions.

Thanks, Sruthi

amerine commented 1 year ago

I have a client that would really appreciate some movement on this.

Avenza commented 1 year ago

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!

davidlowry commented 1 year ago

This wasn't flagged here, but: 1) Alongside HTTP/2, IPV6 is the last item on the Router v2 Roadmap detailed here: https://devcenter.heroku.com/articles/heroku-runtime-router-2-0 (how to enable and disable the BETA) 2) Changelog entry for the BETA: https://devcenter.heroku.com/changelog-items/2682 3) An update here: https://blog.heroku.com/router-2dot0-the-road-to-beta

Good to see :)

sivaneshanms commented 7 months ago

Does Expedited WAF helps for this case?