Skip to main content
10 events
when toggle format what by license comment
Oct 17, 2018 at 3:04 answer added Paul Sweatte timeline score: 0
Apr 5, 2018 at 0:11 history tweeted twitter.com/super_user/status/981685687803052032
Jan 30, 2018 at 9:12 comment added DaveRandom @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
Jan 29, 2018 at 18:32 comment added Adam McCormick @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
Jan 29, 2018 at 15:01 comment added DaveRandom @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.
Apr 13, 2017 at 12:14 history edited CommunityBot
replaced http://serverfault.com/ with https://serverfault.com/
Jul 8, 2015 at 20:59 comment added Adam McCormick @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.
Jul 8, 2015 at 16:59 comment added Hennes 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.
Jul 6, 2015 at 18:12 history migrated from serverfault.com (revisions)
Jul 6, 2015 at 17:44 history asked Adam McCormick CC BY-SA 3.0