Previously Mike Orr wrote: > > On Mon, Jul 7, 2008 at 6:54 AM, Damjan <[EMAIL PROTECTED]> wrote: > > > > > >> > Hi all. I think a better solution is for devlopment.ini to listen > >> > only on localhost by default. I've opened a ticket for > >> > it:http://pylonshq.com/project/pylonshq/ticket/483 > >> > >> That's a great idea -- and should be implemented! > >> > >> However, just to play devil's advocate - if you're tossing pylons > >> behind nginx/lighty/etc, you're going to be serving everything to > >> localhost -- even remote requests. > > > > On linux at least you can also setup an application to listen on > > 127.0.0.2 .. if this is the same for other platforms, you can set the > > development.ini to 127.0.0.2, production on 0.0.0.0 or 127.0.0.1 :) > > That's what localnet is for -- all of 127.0.0.1 to 127.255.255.254 are > your own computer, for those occasions where you need 16,581,373 > different IPs to test your new multiservice application (perhaps a > Twisted Names application). Well, it *was* assigned in the days > before IP scarcity. > > Of course, never leave it to Microsoft to let a mere standard get in > it's way, so somebody with Windows will have to test whether it works > there.
I happened to be tinkering a bit on a XP test. A quick test showed that you can at least ping the entire 127/8 address space in XP. I would expect that you can bind to those addresses as well, but I couldn't quickly test that (no python installed). Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
