Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Why is not something we can answer. We end users can only guess. MS might have good reason (e.g. performance gains?) but you would need to ask the MS engineers why the resolution of localhost to 127.1 is handled internally.
    – Hennes
    Commented Jul 8, 2015 at 16:59
  • @Hennes: The link I posted actually addresses the why pretty well (IPv6 transition), my question is how to get the old functionality given the change. Commented Jul 8, 2015 at 20:59
  • @AdamMcCormick did you ever manage to figure out how to do this? I am assuming there will be some (possibly undocumented) registry setting. I'm building a DNS resolver and I'm trying to work out if it's 100% safe for me to hard-code 127.0.0.1/::1 or there is some place I need to check for whether it has been changed. ftr I don't believe it's a good idea to change localhost, because many applications expect to be able to use it interchangeably with 127.0.0.1, e.g. some server application might bind explicitly to the IP address but its client app will use the name.
    – DaveRandom
    Commented Jan 29, 2018 at 15:01
  • @DaveRandom No, I never did. We had to change the CORS constraints. That said, It's been two and a half years so it may be resolved either for Window 8 or Windows 10 or both Commented Jan 29, 2018 at 18:32
  • @AdamMcCormick if there is a way to do it, no-one anywhere on the internet seems to know how, I'm just going to hard-code them and when someone reports it as a bug I will ask them how they did it :-P
    – DaveRandom
    Commented Jan 30, 2018 at 9:12