On Oct 4, 2:15 am, Amelia T Cat wrote:
> On Mon, 03 Oct 2011 10:09:59 -0700, sillyou su wrote:
> > 啊！！
>
> > I should use 127.0.0.1 instance of 0.0.0.0
>
> Theoretically either one should be fine. If you use 127.0.0.1 it will
> only expose the service to your local machine. If you use 0.0.0.0 ut
Something is running in your port 8080. Change the port and try again.
On Mon, Oct 3, 2011 at 3:15 PM, Amelia T Cat wrote:
> On Mon, 03 Oct 2011 10:09:59 -0700, sillyou su wrote:
>
> > 啊！！
> >
> > I should use 127.0.0.1 instance of 0.0.0.0
>
> Theoretically either one should be fine. If you use
On Mon, 03 Oct 2011 10:09:59 -0700, sillyou su wrote:
> 啊！！
>
> I should use 127.0.0.1 instance of 0.0.0.0
Theoretically either one should be fine. If you use 127.0.0.1 it will
only expose the service to your local machine. If you use 0.0.0.0 ut will
expose the service to other computers on t
On Mon, 03 Oct 2011 10:05:15 -0700, sillyou su wrote:
> I am running web.py on my computer
Does "netstat -nat | grep 8080" show anything listening on port 8080?
(I'm assuming here that you're running on a Linux box)
--
http://mail.python.org/mailman/listinfo/python-list
I am running web.py on my computer
--
http://mail.python.org/mailman/listinfo/python-list
Are you running web.py on your computer, or is it running for example on
a hosting company's computer? If it's not on your computer you have your
port 8080 traffic blocked the hosting company's firewall.
On Sun, 02 Oct 2011 20:59:40 -0700, sillyou su wrote:
> i am learning webpy and I am follow
